Point cloud encoding and decoding method, encoder, and decoder

ABSTRACT

A point cloud encoding and decoding method, an encoder, and a decoder are provided. The encoder determines a processing order of point cloud data during point cloud encoding. The encoder determines a coordinate-axis-order index corresponding to the processing order. The encoder encodes the coordinate-axis-order index and signals encoded bits into a bitstream. The encoder processes the point cloud data according to the processing order, to obtain point cloud data to-be-encoded. The encoder encodes the point cloud data to-be-encoded and signals encoded bits into the bitstream. The decoder parses a bitstream to obtain a coordinate-axis-order index, determines a processing order of point cloud data during point cloud decoding according to the coordinate-axis-order index, parses the bitstream to obtain recovered data of the point cloud data, and determines a position of coordinate data of the point cloud data in a storage unit of the recovered data according to the processing order.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of International Application No.PCT/CN2020/090677, filed May 15, 2020, which claims priority to and thebenefit of U.S. Provisional application patent Ser. No. 62/870,553,filed Jul. 3, 2019, the entire disclosures of which are herebyincorporated by reference.

TECHNICAL FIELD

This disclosure relates to the technical field of video coding, and inparticularly to a point cloud encoding and decoding method, an encoder,and a decoder.

BACKGROUND

In an encoder framework of geometry-based point cloud compression(G-PCC), geometry information of the point cloud and attributeinformation corresponding to each point cloud are encoded separately.After encoding of the geometry information is completed, the geometryinformation is reconstructed. Encoding of the attribute information willdepend on the reconstructed geometry information.

Currently, the encoding of the attribute information mainly aims atencoding of colour information. First, the colour information istransformed from a RGB colour space to a YUV colour space. Thereafter,use the reconstructed geometry information to recolor the point cloud,so that un-encoded attribute information can correspond to thereconstructed geometry information. During encoding of the colourinformation, there are mainly two transform methods. One isdistance-based lifting transform which relies on level of detail (LOD)partition. The other is regional adaptive hierarchical transform (RAHT)which is performed directly. Both methods transform the colourinformation from a spatial domain to a frequency domain, obtainhigh-frequency coefficients and low-frequency coefficients throughtransform, finally quantize the coefficients, and encode to generate abinary bitstream.

However, in RAHT, for any point cloud, the same fixed order is used toperform RAHT, which does not fully show transform efficiency of RAHT.Thus, the transform efficiency is low, reducing coding (i.e., encodingand decoding) efficiency.

SUMMARY

In a first aspect, implementations of this application provide a pointcloud encoding method. The method is implemented in an encoder andincludes the following. A processing order of point cloud data duringpoint cloud encoding is determined, where the processing order indicatesa coordinate axis processing order of three-dimensional coordinates ofthe point cloud data and the point cloud data is all or part of data inpoint cloud. A coordinate-axis-order index corresponding to theprocessing order is determined. The coordinate-axis-order index isencoded and encoded bits are signalled into a bitstream. The point clouddata is processed according to the processing order, to obtain pointcloud data to-be-encoded. The point cloud data to-be-encoded is encodedand encoded bits are signalled into the bitstream.

In a second aspect, implementations of this application provide a pointcloud decoding method. The method is implemented in a decoder andincludes the following. A bitstream is parsed to obtain acoordinate-axis-order index. A processing order of point cloud dataduring point cloud decoding is determined according to thecoordinate-axis-order index, where the processing order indicates acoordinate axis processing order of three-dimensional coordinates of thepoint cloud data and the point cloud data is all or part of data inpoint cloud. The bitstream is parsed to obtain recovered data of thepoint cloud data. A position of coordinate data of the point cloud datain a storage unit of the recovered data is determined according to theprocessing order.

In a third aspect, implementations of this application provide anencoder. The encoder includes at least one processor and a memory. Thememory is coupled to the at least one processor and stores at least onecomputer executable instruction thereon which, when executed by the atleast one processor, causes the at least one processor to execute themethod of the first aspect.

In a fourth aspect, implementations of this application provide adecoder. The decoder includes at least one processor and a memory. Thememory is coupled to the at least one processor and stores at least onecomputer executable instruction thereon which, when executed by the atleast one processor, causes the at least one processor to execute themethod of the second aspect.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a process of geometry-based point cloudcompression (G-PCC) encoding.

FIG. 2 is a block diagram of a process of G-PCC decoding.

FIG. 3 is schematic diagram 1 of spatial encoding.

FIG. 4 is schematic diagram 2 of spatial encoding.

FIG. 5 is schematic diagram 3 of spatial encoding.

FIG. 6 is schematic diagram 4 of spatial encoding.

FIG. 7 is schematic diagram 1 of region adaptive hierarchal transform(RAHT).

FIG. 8 is schematic diagram 2 of RAHT.

FIG. 9 is schematic diagram 3 of RAHT.

FIG. 10 is schematic diagram 1 of an implementation process of pointcloud encoding.

FIG. 11 is schematic diagram 2 of an implementation process of pointcloud encoding.

FIG. 12 is schematic diagram 1 of an implementation process of pointcloud decoding.

FIG. 13 is schematic diagram 2 of an implementation process of pointcloud decoding.

FIG. 14 is schematic diagram 1 of a structure of an encoder.

FIG. 15 is schematic diagram 2 of a structure of an encoder.

FIG. 16 is schematic diagram 1 of a structure of a decoder.

FIG. 17 is schematic diagram 2 of a structure of a decoder.

DETAILED DESCRIPTION

For a more detailed understanding of features and technical contents ofimplementations of this application, realization of the implementationsof this application will be described in detail below with reference tothe accompanying drawings. The attached accompanying drawings are merelyfor reference and description, but are not used to limit theimplementations of this application.

In the implementations of this application, in an encoder framework ofgeometry-based point cloud compression (G-PCC) of point cloud, afterpoint cloud of an input three-dimensional image model is partitionedinto slices, each slice is encoded independently.

FIG. 1 is a block diagram of a process of G-PCC encoding. As illustratedin the block diagram of the process of the G-PCC encoding of FIG. 1, itis applied to a point cloud encoder. For point cloud data to-be-encoded,through slice partition, the point cloud data is first partitioned intomultiple slices. In each slice, geometry information of the point cloudand attribute information corresponding to each point cloud are encodedseparately. During encoding of the geometry information, performcoordinate transform on the geometry information to so that all of thepoint cloud is contained in a bounding box, and then quantify, whichmainly plays a role of scaling. Due to the rounding of quantifying, thegeometry information of part of the point cloud is the same, so decidewhether to remove duplicate points based on parameters. The process ofquantifying and removing the duplicate points is also called thevoxelization. Thereafter, perform octree partition on the bounding box.During encoding of the geometry information based on octree, thebounding box is equally partitioned into eight sub-cubes, and non-empty(including points in the point cloud) sub-cubes are continued to bepartitioned into eight equal parts until leaf nodes obtained throughpartition are 1×1×1 unit cubes. Perform arithmetic coding on nodes inthe leaf nodes to generate a binary geometry bitstream, that is,geometry code stream. During encoding of the geometry information basedon triangle soup (trisoup), octree partition is also performed first.Different from the encoding of the geometry information based on octree,the trisoup does not need to partition the point cloud step by step intounit cubes each with an edge length of 1×1×1, but partitions the pointcloud into blocks each with an edge length of W and then stops thepartition. Based on a surface formed by distribution of the point cloudin each block, at most twelve vertexes generated by both the surface andtwelve edges of the block are obtained. Perform arithmetic coding on thevertexes (surface fitting based on vertexes), to generate a binarygeometry bitstream, that is, geometry code stream. The vertexes are alsoused in implementation of geometry reconstruction and reconstructedgeometry information is used when the attribute information of the pointcloud is encoded.

During encoding of the attribute information, after the encoding of thegeometry information is completed and the geometry information isreconstructed, colour transform is performed, that is, colourinformation (i.e., the attribute information) is transformed from a RGBcolour space to a YUV colour space. Thereafter, use the reconstructedgeometry information to recolor the point cloud, so that attributeinformation that has not been encoded can correspond to thereconstructed geometry information. The encoding of the attributeinformation mainly aims at encoding of the colour information. Duringthe encoding of the colour information, there are mainly two transformmethods. One is distance-based lifting transform which relies on levelof detail (LOD) partition. The other is regional adaptive hierarchicaltransform (RAHT) which is performed directly. Both methods transform thecolour information from a spatial domain to a frequency domain, obtainhigh-frequency coefficients and low-frequency coefficients throughtransform, and finally quantize the coefficients (i.e., quantizedcoefficients). At last, after octree partition and surface fitting,geometry encoding data and quantized coefficient processing attributeencoding data are slice-synthesized, and vertex coordinates of eachblock are encoded in turn (that is, arithmetic coding), to generate abinary attribute bitstream, that is, attribute code stream.

FIG. 2 is a block diagram of a process of G-PCC decoding. As illustratedin the block diagram of the process of the G-PCC decoding of FIG. 2, itis applied to a point cloud decoder. For the obtained binary bitstream,first, the geometry bitstream and the attribute bitstream in the binarybitstream are decoded independently. When decoding the geometrybitstream, the geometry information of the point cloud is obtainedthrough arithmetic decoding-octree synthesis-surfacefitting—reconstructing geometry—inverse coordinate transform. Whendecoding the attribute bitstream, the attribute information of the pointcloud is obtained through arithmetic decoding-inversequantization-LOD-based lifting inverse transform or RAHT-based inversetransform-inverse colour transform. The three-dimensional image model ofthe point cloud data to-be-encoded is restored based on the geometryinformation and the attribute information.

As illustrated in the block diagram of the process of the G-PCC encodingof FIG. 1, RAHT is a part where the attribute information of the pointcloud is encoded. It uses the Harr wavelet transform principle toperform lossy encoding, generally suitable for sparse point cloud.Specifically, before RAHT, geometric coordinate information of the pointcloud has been obtained. The coordinate information of points can beused to obtain a Morton code corresponding to each point in the pointcloud. The Morton code is also called z-order code, because its encodingorder is in spatial z-order. Specifically, the method of calculatingMorton code is described as follows. For three-dimensional coordinateswith each component represented by a d-bit binary digit, the threecoordinate components are represented by the following formula.

$\begin{matrix}{x = {\sum\limits_{l = 1}^{d}{2^{d - l}x_{l}}}} & (1) \\{y = {\sum\limits_{l = 1}^{d}{2^{d - l}y_{l}}}} & (2) \\{z = {\sum\limits_{l = 1}^{d}{2^{d - l}z_{l}}}} & (3)\end{matrix}$

x_(l), y_(l), z_(l)∈{0,1} are respectively binary values correspondingto the highest bit (l=1) to the lowest bit (l=d) of x, y, z. The Mortoncode M is, for x, y, z, from the highest bit to the lowest bit,alternately sorting x_(l), y_(l), z_(l). The calculation formula of M isas follows.

$\begin{matrix}{M = {{\sum\limits_{l = 1}^{d}{2^{3{({d - l})}}\left( {{4x_{l}} + {2y_{l}} + z_{l}} \right)}} = {\sum\limits_{l^{\prime} = 1}^{3d}{2^{{3d} - l^{\prime}}m_{l^{\prime}}}}}} & (4)\end{matrix}$

m_(l′)∈{0,1} are values from the highest bit (l′=1) to the lowest bit(l′=3d) of M. After the Morton code M of each point in the point cloudis obtained, the points in the point cloud are sorted in an ascendingorder according to the Morton code, and a weight w of each point is setto be 1. It is represented as a computer language, similar to acombination of z|(y<<1)|(x<<2).

FIG. 3 is schematic diagram 1 of spatial encoding. FIG. 4 is schematicdiagram 2 of spatial encoding. Combining FIG. 3 and FIG. 4 fordescription, an example where a sorting order from the high bit to thelow bit is z, y, x (x|(y<<1)|(z<<2)) is described.

FIG. 3 illustrates spatial encoding of each pixel of an 8*8 image, from000000 to 111111, using a one-dimensional binary number to encodeposition coordinates of values of x and y at 0-7. Interleave binarycoordinate values to obtain a binary z-value map. Connect the z-shape ina numerical direction, to generate a recursive z-shaped curve. At eachposition in the figure, the z value is placed in the connection order.In fact, the above figure is iteratively generated in the Z direction.From 00 to 11 (one z in the entire figure), then from 0000 to 1111(place one z at each point of the previous z), and then from 000000 to111111 (place one z at each point of the previous z), increase two bitseach time, increasing recursively.

Exemplarily, FIG. 4 illustrates 2×2, 4×4, 8×8, and 16×16 spatialencoding orders, from which it can be seen that the encoding order ofthe Morton code is implemented according to the spatial z-order.

FIG. 5 is schematic diagram 3 of spatial encoding. FIG. 6 is schematicdiagram 4 of spatial encoding. This is the case of extending to threedimensions. The recursive process is illustrated in FIG. 5 and FIG. 6,which achieves coordinate interleaving. The whole process is tocontinuously scatter the coordinate values. x|(y<<1)|(z<<2); that is,each coordinate value is scattered, and is interleaved in turn, first z,then y, and finally x. The decoding process is the aggregation process.

RAHT is performed based on a hierarchical structure which is obtained byperforming octree partition on the point cloud data. From the bottomlayer of the octree, the transform is performed hierarchically. FIG. 7is schematic diagram 1 of RAHT. As illustrated in FIG. 7, voxel block 1is obtained after the octree partition is completed (that is, thegeometry with three alternating colour depths in FIG. 7, where eachsquare represents a point in the point cloud). RAHT is performed fromthe bottom layer, and as an example, the transform order is the X-Y-Zorder. As illustrated in FIG. 7, RAHT is performed first in the Xdirection. If there are neighbouring voxel blocks in the X direction,RAHT is performed on them, to obtain the weighted average (DCcoefficient) and residual (AC coefficient) of attribute values of thetwo neighbouring points. The obtained DC coefficient exists as attributeinformation of voxel block 2 of the parent node, and RAHT is performedat the next layer; while the AC coefficient is kept and used in thefinal encoding. If there is no neighbouring point, the attribute valueof this voxel block is directly transferred to the parent node at thesecond layer. At the second layer, RAHT is performed in the Y direction,if there are neighbouring voxel blocks in the Y direction, RAHT isperformed on them, to obtain the weighted average (DC coefficient) andresidual (AC coefficient) of the attribute values of the twoneighbouring points. Thereafter, at the third layer, RAHT is performedin the Z direction, and voxel block 3 of the parent node with threealternating colour depths is obtained as the child node at the nextlayer in the octree. Repeat RAHT in the x, y, and Z directions untilthere is only one parent node in the entire point cloud.

In practice, when the points in the point cloud are traversed, thesorted Morton code of the point cloud is used. That is, whether twochild nodes are under a same parent node are determined by determiningwhether values after the Morton code is shifted by one bit to the rightare equal.

For the attribute values c₁, c₂ of the two neighbouring points, thespecific RAHT process is as follows:

$\begin{matrix}{\begin{bmatrix}{DC} \\{AC}\end{bmatrix} = {\begin{bmatrix}{1 - b} & b \\{- \frac{1}{a}} & \frac{1}{a}\end{bmatrix}\begin{bmatrix}c_{1} \\c_{2}\end{bmatrix}}} & (5) \\{where} & \; \\{w = {w_{1} + w_{2}}} & (6) \\{b = \frac{w_{1}}{w_{1} + w_{2}}} & (7) \\{a = {\sqrt{({luma})^{2}\frac{w_{1} + w_{2}}{w_{1}w_{2}}}.}} & (8)\end{matrix}$

luma is configured with incoming quantized parameters, and w is theweight corresponding to the DC coefficient, which is obtained throughcalculation. The DC coefficient is the weighted average of theattributes, and the AC coefficient is the residual of the attributes ofthe two neighbouring points. At the first layer, the attribute valuesc₁, c₂ correspond to w₁, w₂, used to calculate DC coefficient values atthe other layers.

In the implementations of this application, the specific steps of RAHTare as follows.

(1) Use the attribute values of the points in the point cloud as DCcoefficients at the first layer and set their weights to be 1, and startRAHT.

(2) The DC coefficient and AC coefficient at this layer are filled intothe parent layer and parent node at the next layer according to thecorresponding index, if any. Leave it blank if there is no ACcoefficient.

(3) According to each index sorted based on the Morton code, traversethe DC coefficient corresponding to the index.

(4) Shift Morton codes corresponding to all DC coefficients by one bitto the right. In this case, the Morton code of each DC coefficientrepresents the Morton code of its parent node.

(5) FIG. 8 is schematic diagram 2 of RAHT. As illustrated in FIG. 8,determine whether Morton codes of two DC coefficients are the same. Ifthey are the same, they are under the same parent node. RAHT isperformed on them, the obtained DC coefficient is filled into the DCcoefficient of the parent node at the next layer and the AC coefficientis filled into the last DC coefficient at the next layer, and the weightof the sum of the two DC coefficients is assigned to the DC coefficientof the parent node. If they are different, fill this DC coefficient andits weight directly into the next layer.

(6) Repeat (2)-(5) until there is only one DC coefficient in a certainlayer.

(7) Finally, the DC coefficients are quantized, and the DC coefficientsand AC coefficients of the attribute values at this layer are encoded.

Accordingly, in the block diagram of the decoder, the transform order ofRAHT also needs to be used in the inverse RAHT.

The following describes RAHT in the decoding process.

RAHT in decoding process is inverse transform of RAHT in encodingprocess. The same as the encoding process, before the inverse transformis performed, first calculate the Morton code of each point in the pointcloud. After the Morton code M of each point is obtained, sort thepoints in the point cloud in an ascending order and set the weight ofeach point to be 1. In the inverse RAHT, all points in the point cloudare traversed according to the order of the sorted Morton code.

Since RAHT is performed in a layered manner, from the bottom layer, theneighbouring points in the point cloud are determined layer by layer,and RAHT is performed on the attribute value according to the weight.The inverse RAHT starts from the top layer and is from top to bottom.Therefore, before the inverse RAHT, the weight information of each layerneeds to be obtained.

Before the inverse RAHT, using the obtained Morton code information,starting from the bottom layer, at the encoding end, RAHT is performedat each layer and neighbouring nodes are determined, and then the weightinformation of each layer and the corresponding position of the ACcoefficient can be obtained. Each time RAHT is performed at each layer,the corresponding Morton code is shifted by one bit to the left. Theweight information, and the Morton code information corresponding tonodes in each layer are recorded in the buffer, for later use.

In the inverse RAHT, from the top layer, the neighbouring nodes aredetermined according to the Morton code information of each layer, andthe inverse RAHT is performed using the obtained weight information andthe decoded attribute information. FIG. 9 is schematic diagram 3 ofRAHT. As illustrated in FIG. 9, the inverse RAHT is equivalent to theprocess from the (k+1)-th layer to the k-th layer. When the neighboringnodes are determined, the traversed DC coefficients and thecorresponding AC coefficients are used to perform the inverse transformof RAHT.

In more detail, for the attribute values c₁, c₂ of the two neighbouringpoints, the specific inverse RAHT process is illustrated in thefollowing formula.

$\begin{matrix}{\begin{bmatrix}c_{1} \\c_{2}\end{bmatrix} = {\begin{bmatrix}1 & {- {ab}} \\1 & {a\left( {1 - b} \right)}\end{bmatrix}\begin{bmatrix}{DC} \\{AC}\end{bmatrix}}} & (9)\end{matrix}$

Specifically, when RAHT is performed on the attribute information of thepoint cloud in a layered manner, RAHT is performed iteratively for eachnode along three axes in a fixed order in each layer. However, for anypoint cloud, using the same fixed order to perform RAHT does not fullydemonstrate the transform efficiency of RAHT. For example, currently, inG-PCC, the fixed order generally used is ZYX, but there are otherpossible transform orders, such as X-Y-Z. The use of the ZYX order forperforming RAHT on the nodes in the point cloud leads to low transformefficiency, which reduces the coding efficiency.

To overcome the above drawbacks, implementations of this applicationprovide a point cloud encoding and decoding method, an encoder, adecoder, and a computer storage medium. At the encoding side, theencoder can first determine the processing order of transformcorresponding to the point cloud data, signal the processing order intothe bitstream while performing RAHT according to the processing order,and transmit the processing order to the decoder. At the decoding side,the decoder parses the bitstream to obtain the processing order of thetransform corresponding to the point cloud data, so that RAHT can beperformed according to the processing order. It can be seen, in thepoint cloud encoding and decoding method provided in this application,for all or part of data in the point cloud, a fixed order is no longerused to perform RAHT, but a syntax element in the bitstream is used toindicate the processing order. In this way, the coordinate processingorder during coding can be changed adaptively and the transformefficiency of RAHT can be further fully showed. As such, the problem oflow transform efficiency can be solved and the coding efficiency can begreatly improved.

It is understandable that, in this application, the point cloud encodingmethod in the implementations of this application can be applied to RAHTas illustrated in FIG. 1. Accordingly, the point cloud decoding methodof the implementations of this application can also be applied to RAHTas illustrated in FIG. 2. In other words, the point cloud encoding anddecoding method in the implementations of this application can beapplied to a video encoding system or a video decoding system, or evento both a video encoding system and a video decoding system, which isnot specifically limited in the implementations of this application.

The technical solutions in the implementations of this application willbe clearly and completely described below in conjunction with thedrawings in the implementations of this application.

A point cloud encoding method is provided in an implementation of thisapplication. FIG. 10 is schematic diagram 1 of an implementation processof point cloud encoding. As illustrated in FIG. 10, in theimplementation of this application, a method performed by an encoder forencoding point cloud data includes the following.

At 101, a processing order of point cloud data during point cloudencoding is determined, where the processing order indicates acoordinate axis processing order of three-dimensional coordinates of thepoint cloud data and the point cloud data is all or part of data inpoint cloud.

In the implementation of this application, the encoder can firstdetermine the processing order of the point cloud data during pointcloud encoding. The point cloud data is all or part of data in the pointcloud and the processing order can be used to indicate the coordinateaxis processing order of the three-dimensional coordinates of the pointcloud data.

It is understandable that, in the implementation of this application,the point cloud data may be all data in the point cloud. Accordingly,determining the processing order of the point cloud data meansdetermining a processing order of all data in the point cloud. That is,in this application, for each point in the point cloud, the encoder mayuse the same processing order for transform.

Furthermore, in the implementation of this application, the encoder canobtain multiple slices corresponding to the point cloud by partitioningthe point cloud. Therefore, the point cloud data can also be part ofdata in the point cloud, that is, the point cloud data can be data ofany slice in the point cloud. Accordingly, determining the processingorder of the point cloud data is determining a processing order of dataof any slice in the point cloud. That is, in this application, for eachpoint of the same slice in the point cloud, the encoder may use the sameprocessing order for transform.

It is understandable that, in the implementation of this application,the processing order is a transform order used in RAHT. Each point inthe point cloud is point cloud data with three dimensions of X, Y, andZ. Therefore, the processing order indicates the order in which thetransform is sequentially performed in the three coordinate axes of X,Y, and Z.

Exemplary, in the implementation of this application, when RAHT isperformed on attribute information of the point cloud in a hierarchicalmanner, in each layer, based on the processing order, RAHT is performediteratively for each node along three axes. For example, if theprocessing order is X-Y-Z, the encoder can perform RAHT on the nodes inthe point cloud first in X axis, then in Y axis, and last in Z axis. Ifthe processing order is Y-Z-X, then the encoder can perform RAHT on thenodes in the point cloud first in Y axis, then in Z axis, and last in Xaxis.

It is understandable that, in the implementation of this application,because each point in the point cloud is point cloud data with threedimensions of X, Y, and Z, the order in which the encoder performs RAHTcan include six different combinations, that is, the processing ordercan include six different transform orders.

Furthermore, in the implementation of this application, the processingorder is any of a Z-Y-X order, an X-Y-Z order, an X-Z-Y order, a Y-Z-Xorder, a Z-X-Y order, and a Y-X-Z order, and X, Y, Z are coordinate axesof the three-dimensional coordinates of the point cloud data.

It should be noted that, in the implementation of this application, whendetermining the processing order of the point cloud data during pointcloud encoding, the encoder can determine the processing order accordingto a Morton code of each node in the point cloud data.

Specifically, in the implementation of this application, the encoder canfirst calculate the Morton code of each node in the point cloud data,then sort the nodes in the point cloud data according to an ascendingorder of the Morton code, and finally traverse each node in the pointcloud data in the sorted order.

At 102, a coordinate-axis-order index corresponding to the processingorder is determined.

In the implementation of this application, after determining theprocessing order of the point cloud data during point cloud encoding,the encoder can further determine the coordinate-axis-order index (i.e.,index number) corresponding to the processing order.

It is understandable that, for different processing orders, the encodercan set different coordinate-axis-order indexes. Accordingly, since theprocessing order can be any of six different transform orders, thecoordinate-axis-order index can also include six different values.

Furthermore, in the implementation of this application, when the encoderdetermines the coordinate-axis-order index corresponding to theprocessing order, the encoder can set a value of thecoordinate-axis-order index corresponding to the processing orderaccording to a correspondence table between preset indexes andprocessing orders.

Specifically, in this application, Table 1 is a correspondence table 1between preset indexes and processing orders. As illustrated in Table 1,for different processing orders, a corresponding coordinate-axis-orderindex can be determined by querying the correspondence table between thepreset indexes and the processing orders.

TABLE 1 coordinate-axis-order index processing order 0 Z-Y-X order 1X-Y-Z order 2 X-Z-Y order 3 Y-Z-X order 4 Z-Y-X order 5 Z-X-Y order 6Y-X-Z order 7 X-Y-Z order

It can be seen from Table 1 above that, in this application, theprocessing order and the coordinate-axis-order index are not inone-to-one correspondence. For six kinds of transform orders of RAHT,the Z-Y-X order corresponds to two different coordinate-axis-orderindexes. Specifically, the Z-Y-X order corresponds to index 0 and index4, respectively. The X-Y-Z order corresponds to two differentcoordinate-axis-order indexes. Specifically, the X-Y-Z order correspondsto index 1 and index 7, respectively. The other four RAHT orders otherthan the Z-Y-X order and the X-Y-Z order respectively correspond to aunique coordinate-axis-order index. The X-Z-Y order corresponds to index2, the Y-Z-X order corresponds to index 3, the Z-X-Y order correspondsto index 5, and the Y-X-Z order corresponds to index 6.

Exemplarily, in this application, the encoder sets the value of thecoordinate-axis-order index corresponding to the processing orderaccording to the correspondence table between the preset indexes and theprocessing orders. If the processing order of the point cloud data isthe Z-Y-X order, the encoder can set the value of thecoordinate-axis-order index to be 0 or 4. If the processing order of thepoint cloud data is the X-Y-Z order, the encoder can set the value ofthe coordinate-axis-order index to be 1 or 7. If the processing order ofthe point cloud data is the X-Z-Y order, the encoder can set the valueof the coordinate-axis-order index to be 2. If the processing order ofthe point cloud data is the Y-Z-X order, the encoder can set the valueof the coordinate-axis-order index to be 3. If the processing order ofthe point cloud data is the Z-X-Y order, the encoder can set the valueof the coordinate-axis-order index to be 5. If the processing order ofthe point cloud data is the Y-X-Z order, the encoder can set the valueof the coordinate-axis-order index to be 6.

It should be noted that, in this application, there is no specificconcept of X, Y, and Z coordinate axes in G-PCC. In general, on thebasis of the X, Y, and Z coordinate axes, the coordinate axis processingorder can be represented by 0, 1, and 2. For example, if the processingorder is the X-Y-Z order, it can be indicated by 0-1-2.

Based on Table 1 above, Table 2 is a correspondence table 2 betweenpreset indexes and processing orders. As illustrated in Table 2, fordifferent processing orders, a corresponding coordinate-axis-order indexcan be determined by querying the correspondence table between thepreset indexes and the processing orders.

TABLE 2 coordinate-axis-order index X Y X 0 2 1 0 1 0 1 2 2 0 2 1 3 2 01 4 2 1 0 5 1 2 0 6 1 0 2 7 0 1 2

Exemplarily, in this application, the encoder sets the value of thecoordinate-axis-order index corresponding to the processing orderaccording to the correspondence table between the preset indexes and theprocessing orders. If the processing order of the point cloud data isthe Z-Y-X order, that is, the processing order is indicated by 2-1-0,the encoder can set the value of the coordinate-axis-order index to be 0or 4. If the processing order of the point cloud data is the X-Y-Zorder, that is, the processing order is indicated by 0-1-2, the encodercan set the value of the coordinate-axis-order index to be 1 or 7. Ifthe processing order of the point cloud data is the X-Z-Y order, thatis, the processing order is indicated by 0-2-1, the encoder can set thevalue of the coordinate-axis-order index to be 2. If the processingorder of the point cloud data is the Y-Z-X order, that is, theprocessing order is indicated by 2-0-1, the encoder can set the value ofthe coordinate-axis-order index to be 3. If the processing order of thepoint cloud data is the Z-X-Y order, that is, the processing order isindicated by 1-2-0, the encoder can set the value of thecoordinate-axis-order index to be 5. If the processing order of thepoint cloud data is the Y-X-Z order, that is, the processing order isindicated by 1-0-2, the encoder can set the value of thecoordinate-axis-order index to be 6.

It is understandable that, in this application, thecoordinate-axis-order index can be represented by the syntaxaxis_coding_order, that is, the processing order of the three coordinateaxes X, Y, and Z can be specified by the syntax axis_coding_order.Specifically, based on the above Table 2, the axis_coding_order for theG-PCC standard can be used to process data in the RecPic[pointIdx][axis]buffer. For example, when the value of axis_coding_order is equal to 0,that is, the processing order is Z-Y-X, if the value of axis is equal to0, RecPic[pointIdx][0] stores data of the Z axis; if the value of axisis equal to 1, RecPic[pointIdx][1] stores data of the Y axis; if thevalue of axis is equal to 2, RecPic[pointIdx][2] stores data of the Xaxis.

At 103, the coordinate-axis-order index is encoded and encoded bits aresignalled into a bitstream.

In the implementation of this application, after determining thecoordinate-axis-order index corresponding to the processing order, theencoder can further encode the coordinate-axis-order index and signalthe encoded bits into the bitstream.

Furthermore, in the implementation of this application, when the encoderencodes the coordinate-axis-order index and signals the encoded bitsinto the bitstream, the encoder can first encode thecoordinate-axis-order index by using fixed length coding, determine theencoded bits, and then signal the encoded bits into the bitstream.

It is understandable that, in this application, fixed length codingmeans that any value (probability may be different) of the output symbolsequence of the information source is encoded into an output code wordof the same length, without using the statistical characteristics of theinformation source. After encoding the coordinate-axis-order index byusing fixed length coding, the encoder obtains the fixed length code ofthe same length.

Furthermore, in the implementation of this application, when the encoderencodes the coordinate-axis-order index and signals the encoded bitsinto the bitstream, the encoded bits can be signalled into a bitstreamcorresponding to a data unit of a parameter set, where the data unit ofthe parameter set contains parameters used for decoding the point clouddata.

It should be noted that, in the implementation of this application, theparameter set may be a sequence-layer parameter set.

Furthermore, in the implementation of this application, the parameterset may also be a sequence parameter set.

It should be noted that, in the implementation of this application, thedata unit of the parameter set may contain attribute information of thepoint cloud data and the attribute information is a scalar attribute ora vector attribute associated with a point in the point cloud data.

It can be understood that, in the implementation of this application,the data unit of the parameter set may also contain geometry informationof the point cloud data and the geometry information is Cartesiancoordinates associated with a point in the point cloud data.

Furthermore, in the implementation of this application, when the encoderencodes the coordinate-axis-order index and signals the encoded bitsinto the bitstream, the encoded bits can be signalled into a data unitwhere auxiliary information of the bitstream is located.

Exemplarily, in the implementation of this application, the auxiliaryinformation may be video usability information (VUI).

The video usability information provides additional information for thecorresponding bitstream to allow wider application for users. Forexample, in the bitstream constraint information, the video usabilityinformation specifies: (1) whether the motion crosses the boundary ofthe picture; (2) the maximum byte per picture; (3) the maximum bit permacro block; (4) the length of the maximum motion vector (horizontal andvertical); (5) the number of resorted frames; (6) the size of themaximum decoded frame buffer. When the decoder sees this information,the decoder does not use the “level” information to set the decodingrequirements (which is generally higher than the actual requirements ofthe bitstream), but can customize its decoding operations based onstricter constraints.

Exemplarily, in the implementation of this application, the auxiliaryinformation may also be supplemental enhancement information (SEI). SEIis a concept in the category of bitstream, which provides a way to addinformation to the video bitstream, and is one of the characteristics ofthe H.264/H.265 video compression standard.

SEI is not a necessary option for the decoding process, which may behelpful to the decoding process (error tolerance, error correction) andcan be integrated in the video bitstream. That is, when the encoderoutputs the video bitstream, it may not provide SEI, or the SEI may bediscarded for some reason at the video transmission process,de-capsulation, and decoding.

It can be understood that, in the implementation of this application,when the encoder encodes the coordinate-axis-order index and signals theencoded bits into the bitstream, the encoded bits can be signalled intoa transmission stream containing point cloud encoding data correspondingto the point cloud data. That is, the bitstream can be the transmissionstream containing the point cloud encoding data.

Furthermore, in the implementation of this application, when the encoderencodes the coordinate-axis-order index and signals the encoded bitsinto the bitstream, the encoded bits can be signalled into a media filecontaining point cloud encoding data corresponding to the point clouddata. That is, the bitstream can be the media file containing the pointcloud encoding data.

That is, in this application, the coordinate-axis-order indexaxis_coding_order can be encoded in the auxiliary information (forexample, VUI) of the sequence parameter set (SPS), encoded in the dataunit of other auxiliary information (for example, SEI) of the pointcloud data, or also be encoded in the unit of the auxiliary informationin the format of transmission stream or file.

At 104, the point cloud data is processed according to the processingorder, to obtain point cloud data to-be-encoded.

In the implementation of this application, after determining theprocessing order of the point cloud data during point cloud encoding,that is, after 101, the encoder processes the point cloud data accordingto the processing order, to obtain point cloud data to-be-encoded.

It can be understood that, in the implementation of this application,the processing order is the transform order when RAHT is performed onthe attribute information of the point cloud. Therefore, after theencoder determines the processing order, it can use the processing orderto perform RAHT on the point cloud data, so as to obtain thecorresponding point cloud data to-be-encoded.

It should be noted that, in the implementation of this application,since the point cloud data may be all data in the point cloud, theprocessing order may be the transform order of all data in the pointcloud. Furthermore, after determining the processing order, the encodercan sequentially perform RAHT on each point in the point cloud accordingto the processing order.

Furthermore, in the implementation of this application, since the pointcloud data may also be part of data in the point cloud, that is, thepoint cloud data may be data of any slice in the point cloud, theprocessing order can also be the transform order of part of data in thepoint cloud. Furthermore, after determining the processing ordercorresponding to a certain slice in the point cloud, the encoder cansequentially perform RAHT on each point in this slice according to theprocessing order.

That is to say, in this application, if the processing order is thetransform order of all data in the point cloud, the encoder can use thesame transform order to perform RAHT on the all data in the point cloud.If the processing order is the transform order of part of data in thepoint cloud, the encoder can use the same transform order to performRAHT on the part of data in the point cloud. For example, for data in aslice after partition, the same transform order can be used for RAHT.

Furthermore, in the implementation of this application, when the encoderprocesses the point cloud data according to the processing order, toobtain the point cloud data to-be-encoded, the encoder can first performcoordinate mapping on the point cloud data according to the processingorder.

Specifically, in the implementation of this application, when theencoder performs coordinate mapping on the point cloud data according tothe processing order, the encoder can rearrange the coordinates of thepoint cloud data according to the processing order.

Furthermore, in the implementation of this application, when the encoderprocesses the point cloud data according to the processing order, toobtain the point cloud data to-be-encoded, the encoder can processsequentially, according to the processing order, the point cloud data ina corresponding coordinate axis direction.

It should be noted that, in this application, the execution process ofRAHT is to: first transform in one coordinate direction, then transformin another coordinate direction, and finally transform in the thirdcoordinate direction.

It can be understood that, in the implementation of this application,when the encoder processes sequentially, according to the processingorder, the point cloud data in the corresponding coordinate axisdirection, the encoder can perform sequentially, according to theprocessing order, RAHT on the point cloud data in the correspondingcoordinate axis direction.

Furthermore, in the implementation of this application, when the decoderperforms sequentially, according to the processing order, RAHT on thepoint cloud data in the corresponding coordinate axis direction, theencoder can first determine a Morton code of a node in the point clouddata and perform RAHT on the point cloud data according to theprocessing order and the Morton code.

Furthermore, in the implementation of this application, when the encoderperforms RAHT on the point cloud data according to the processing orderand the Morton code, the encoder may first determine whether theprocessing order is a same as a preset order.

It can be understood that, in the implementation of this application,the preset order may be a default transform order pre-stored by theencoder. For example, the encoder can set the Z-Y-X order as the presetorder.

Furthermore, in the implementation of this application, the encoder cancompare the processing order with the preset order. The encoder performsRAHT on the point cloud data directly according to the preset order andthe Morton code, if the processing order is the same as the presetorder. The encoder performs RAHT on the point cloud data according tothe processing order and the Morton code, if the processing order isdifferent from the preset order.

It should be noted that, in implementations of this application, FIG. 11is schematic diagram 2 of an implementation process of point cloudencoding. As illustrated in FIG. 11, after the encoder determines theprocessing order of the point cloud data during point cloud encoding,i.e., after 101, and before the encoder determines thecoordinate-axis-order index corresponding to the processing order, i.e.,before 102, the method performed by the encoder for encoding the pointcloud data further includes the following.

At 106, an order indication parameter is determined according to theprocessing order, where the order indication parameter is for indicatingwhether to use the preset order.

At 107, the order indication parameter is encoded and encoded bits aresignalled into the bitstream.

After determining the processing order of the point cloud data, theencoder can first set the order indication parameter according to theprocessing order, then encode the order indication parameter, and writethe encoded bits into the bitstream.

It should be noted that, in the implementation of this application, theorder indication parameter may be used to indicate whether to use thepreset order. That is, if the encoder uses the preset order fortransform, the order indication parameter can be set to indicate thatthe preset order is used. If the encoder does not use the preset orderfor transform, the order indication parameter can be set to indicatethat the preset order is not used.

Furthermore, in the implementation of this application, the encoderdetermines the order indication parameter according to the processingorder. If the processing order is different from the preset order, theencoder needs to transform the point cloud data according to theprocessing order, so a value of the order indication parameter can beset to be indicative of not using the preset order. If the processingorder is the same as the preset order, the encoder can transform thepoint cloud data according to the preset order, so the value of theorder indication parameter can be set to be indicative of using thepreset order.

Exemplarily, in this application, when setting the order indicationparameter, the encoder may set the value of the order indicationparameter to 0, indicating that the preset order is not used, or set thevalue of the order indication parameter to 1, indicating that the presetorder is used.

It is understandable that, in this application, the order indicationparameter can be characterized by the syntaxattr_raht_order_default_flag. Specifically, if the value ofattr_raht_order_default_flag is equal to 1, it indicates that the presetorder is used; if the value of attr_raht_order_default_flag is equal to0, it indicates that the preset order is not used.

At 105, the point cloud data to-be-encoded is encoded and encoded bitsare signalled into the bitstream.

In the implementation of this application, after the encoder processesthe point cloud data according to the processing order to obtain thepoint cloud data to-be-encoded, the encoder can encode the point clouddata to-be-encoded and signal the encoded bits into the bitstream.

According to the point cloud encoding method proposed in the above steps101 to 107, the encoder no longer uses the fixed transform order toperform RAHT on the point cloud data, as proposed in the prior art. Forexample, the X-Y-Z order is used to perform RAHT on all point clouddata. Instead, during encoding the point cloud data, the processingorder corresponding to the point cloud data is determined before thetransform, and then the processing order is used to perform RAHT.

It can be understood that, in this application, from the perspective ofthe processing order of the three coordinates of X, Y, and Z, currently,in G-PCC, the encoder performs transform in a fixed order. In contrast,in the point cloud encoding method proposed in this application, theprocessing order of the encoder on the three coordinates in G-PCC can bechanged adaptively, thereby improving encoding efficiency.

It should be noted that, in this application, the flexibility of theprocessing order can be constrained to the sequence layer, and theentire point cloud can use the same coordinate processing order, thatis, partitions in the point cloud (such as slices) all use the samecoordinate processing order.

It is understandable that, in this application, the encoding end maypreprocess the point cloud data before encoding the point cloud data.Specifically, the encoder can reset the X, Y, and Z coordinate axes ofthe point cloud data and re-determine the processing order. Thereafter,the encoder encodes the preprocessed point cloud data, and from theperspective of display, indicates the preprocessing method at thesequence layer, that is, after encoding the coordinate-axis-order indexcorresponding to the processing order, the encoder signals the encodedbits into the bitstream. Therefore, after the bitstream is transmittedto the decoding end, the decoder decodes the bitstream to obtain thedecoded point cloud, and performs post-processing on the point cloudaccording to the preprocessing method indicated by the sequence layer.That is, the decoding end parses to obtain the coordinate-axis-orderindex, and determines the processing order indicated by thecoordinate-axis-order index, so that the X, Y, and Z coordinate axes ofthe point cloud data can be adaptively set.

Implementations of this application provide the point cloud encodingmethod. The encoder determines the processing order of point cloud dataduring point cloud encoding, where the processing order indicates thecoordinate axis processing order of the three-dimensional coordinates ofthe point cloud data and the point cloud data is all or part of data inthe point cloud. The encoder determines the coordinate-axis-order indexcorresponding to the processing order. The encoder encodes thecoordinate-axis-order index and signals the encoded bits into thebitstream. The encoder processes the point cloud data according to theprocessing order, to obtain the point cloud data to-be-encoded. Theencoder encodes the point cloud data to-be-encoded and signals theencoded bits into the bitstream. That is, in the implementations of thisapplication, at the encoding side, the encoder can first determine theprocessing order of transform corresponding to the point cloud data,signal the processing order into the bitstream while performing RAHTaccording to the processing order, and transmit the processing order tothe decoder. At the decoding side, the decoder parses the bitstream toobtain the processing order of the transform corresponding to the pointcloud data, so that RAHT can be performed according to the processingorder. It can be seen, in the point cloud encoding and decoding methodprovided in this application, for all or part of data in the pointcloud, a fixed order is no longer used to perform RAHT, but a syntaxelement in the bitstream is used to indicate the processing order. Inthis way, the coordinate processing order during coding can be changedadaptively and the transform efficiency of RAHT can be further fullyshowed. As such, the problem of low transform efficiency can be solvedand the coding efficiency can be greatly improved.

Based on the above implementations, a point cloud decoding method isprovided in another implementation of this application. FIG. 12 isschematic diagram 1 of an implementation process of point clouddecoding. As illustrated in FIG. 12, in the implementation of thisapplication, a method performed by a decoder for decoding point clouddata includes the following.

At 201, a bitstream is parsed to obtain a coordinate-axis-order index.

In the implementation of this application, the decoder parses thebitstream to obtain the coordinate-axis-order index of the point clouddata.

It should be noted that, in the implementation of this application, thecoordinate-axis-order index obtained by the decoder through parsing thebitstream may be used to indicate the processing order.

Specifically, in this application, since the processing order can be anyof six different transform orders, the coordinate-axis-order indexobtained by the decoder through parsing may also include six differentvalues.

It is understandable that, in this application, thecoordinate-axis-order index can be represented by the syntaxaxis_coding_order, that is, the processing order of the three coordinateaxes X, Y, and Z can be specified by the syntax axis_coding_order.Specifically, based on the above Table 2, the axis_coding_order for theG-PCC standard can be used to process data in the RecPic[pointIdx][axis]buffer. For example, when the value of axis_coding_order is equal to 0,that is, the processing order is Z-Y-X, if the value of axis is equal to0, RecPic[pointIdx][0] stores data of the Z axis; if the value of axisis equal to 1, RecPic[pointIdx][1] stores data of the Y axis; if thevalue of axis is equal to 2, RecPic[pointIdx][2] stores data of the Xaxis.

Exemplarily, in the G-PCC standard text, the syntax part correspondingto coordinate-axis-order index can be as illustrated in Table 3 below.

TABLE 3 Descriptor seq_parameter_set( ) { ...... axis_coding_order u(3)...... }

Furthermore, in the implementation of this application, when the decoderparses the bitstream to obtain the coordinate-axis-order index, thedecoder can parse a fixed length code to obtain thecoordinate-axis-order index.

It can be understood that, in this application, the fixed length code isthe output code word of the same length obtained after encoding usingfixed length coding. In other words, the encoder obtains the fixedlength code of the same length after encoding the coordinate-axis-orderindex using fixed length coding.

Furthermore, in the implementation of this application, when the decoderparses the bitstream to obtain the coordinate-axis-order index, thedecoder can parse a bitstream corresponding to a data unit of aparameter set in the bitstream, where the data unit of the parameter setcontains parameters used for decoding the point cloud data.

It should be noted that, in the implementation of this application, theparameter set can be a sequence-layer parameter set.

Furthermore, in the implementation of this application, the parameterset can also be a sequence parameter set.

It should be noted that, in the implementation of this application, thedata unit of the parameter set can contain attribute information of thepoint cloud data, where the attribute information is a scalar attributeor a vector attribute associated with a point in the point cloud data.

It is understandable that, in the implementation of this application,the data unit of the parameter set can further contain geometryinformation of the point cloud data, where the geometry information isCartesian coordinates associated with a point in the point cloud data.

Furthermore, in the implementation of this application, when the decoderparses the bitstream to obtain the coordinate-axis-order index, afterthe bitstream is received, the decoder parses a data unit whereauxiliary information of the bitstream is located, to obtain thecoordinate-axis-order index.

Exemplarily, in the implementation of this application, the auxiliaryinformation is VUI.

Exemplarily, in the implementation of this application, the auxiliaryinformation is SEI.

It is understandable that, in the implementation of this application,when the decoder parses the bitstream to obtain thecoordinate-axis-order index, the parsed bitstream can be a transmissionstream containing point cloud encoding data corresponding to the pointcloud data. That is, the bitstream can be the transmission streamcontaining the point cloud encoding data.

Furthermore, in the implementation of this application, when the decoderparses the bitstream to obtain the coordinate-axis-order index, theparsed bitstream can be a media file containing point cloud encodingdata corresponding to the point cloud data. That is, the bitstream canbe the media file containing the point cloud encoding data.

That is, in this application, the coordinate-axis-order indexaxis_coding_order can be encoded in the auxiliary information (forexample, VUI) of the SPS, encoded in the data unit of other auxiliaryinformation (for example, SEI) of the point cloud data, or also beencoded in the unit of the auxiliary information in the format oftransmission stream or file.

At 202, a processing order of point cloud data during point clouddecoding is determined according to the coordinate-axis-order index,where the processing order indicates a coordinate axis processing orderof three-dimensional coordinates of the point cloud data and the pointcloud data is all or part of data in point cloud.

In the implementation of this application, after the decoder parses thebitstream to obtain the coordinate-axis-order index, the decoder candetermine the processing order of the point cloud data during pointcloud decoding according to the coordinate-axis-order index.

It is understandable that, in this application, the processing orderindicates the coordinate axis processing order of the three-dimensionalcoordinates of the point cloud data and the point cloud data is all orpart of data in point cloud.

Furthermore, in the implementation of this application, the processingorder can be used to indicate the coordinate axis processing order ofthe three-dimensional coordinates of the point cloud data.

It is understandable that, in the implementation of this application,the point cloud data may be all data in the point cloud. Accordingly,determining by the decoder the processing order of the point cloud dataduring point cloud decoding according to the coordinate-axis-order indexmeans determining a processing order of all data in the point cloud.That is, in this application, for each point in the point cloud, thedecoder may use the same processing order for transform.

Furthermore, in the implementation of this application, the encoder canobtain multiple slices corresponding to the point cloud by partitioningthe point cloud. Therefore, the point cloud data can also be part ofdata in the point cloud, that is, the point cloud data can be data ofany slice in the point cloud. Accordingly, determining by the decoderthe processing order of the point cloud data during point cloud decodingaccording to the coordinate-axis-order index means determining aprocessing order of data of any slice in the point cloud. That is, inthis application, for each point of the same slice in the point cloud,the decoder may use the same processing order for transform.

It is understandable that, in the implementation of this application,the processing order is a transform order used in RAHT. Each point inthe point cloud is point cloud data with three dimensions of X, Y, andZ. Therefore, the processing order indicates the order in which thetransform is sequentially performed in the three coordinate axes of X,Y, and Z.

Exemplary, in the implementation of this application, when RAHT isperformed on attribute information of the point cloud in a hierarchicalmanner, in each layer, based on the processing order, RAHT is performediteratively for each node along three axes. For example, if theprocessing order is X-Y-Z, the decoder can perform RAHT on the nodes inthe point cloud first in X axis, then in Y axis, and last in Z axis. Ifthe processing order is Y-Z-X, then the decoder can perform RAHT on thenodes in the point cloud in Y axis, then in Z axis, and last in X axis.

It is understandable that, in the implementation of this application,because each point in the point cloud is point cloud data with threedimensions of X, Y, and Z, the order in which the decoder performs RAHTcan include six different combinations, that is, the processing ordercan include six different transform orders.

Specifically, for different processing orders, the encoder can setdifferent coordinate-axis-order indexes. Accordingly, since theprocessing order can be any of six different transform orders, thecoordinate-axis-order index can also include six different values.

Furthermore, in the implementation of this application, the processingorder is any of a Z-Y-X order, an X-Y-Z order, an X-Z-Y order, a Y-Z-Xorder, a Z-X-Y order, and a Y-X-Z order, and X, Y, Z are coordinate axesof the three-dimensional coordinates of the point cloud data.

Furthermore, in the implementation of this application, when the decoderdetermines the processing order of the point cloud data during pointcloud decoding according to the coordinate-axis-order index, theprocessing order corresponding to the coordinate-axis-order index can bedetermined according to a correspondence table between preset indexesand processing orders.

Specifically, in this application, Table 1 above is the correspondencetable 1 between the preset indexes and the processing orders. Asillustrated in Table 1, for different processing orders, thecorresponding coordinate-axis-order index can be determined by queryingthe correspondence table between the preset indexes and the processingorders.

Exemplarily, in this application, the decoder determines the processingorder of the point cloud data during point cloud decoding according tothe coordinate-axis-order index. If the value of thecoordinate-axis-order index is 0 or 4, the decoder can determine thatthe corresponding processing order of the point cloud data is the Z-Y-Xorder. If the value of the coordinate-axis-order index is 1 or 7, thenthe decoder can determine that the corresponding processing order of thepoint cloud data is the X-Y-Z order. If the value of thecoordinate-axis-order index is 2, the decoder can determine that thecorresponding processing order of the point cloud data is the X-Z-Yorder. If the value of the coordinate-axis-order index is 3, the decodercan determine that the corresponding processing order of the point clouddata is the Y-Z-X order. If the value of the coordinate-axis-order indexis 5, then the decoder can determine that the corresponding processingorder of the point cloud data is the Z-X-Y order. If the value of thecoordinate-axis-order index is 6, the decoder can determine that thecorresponding processing order of the point cloud data is the Y-X-Zorder.

It should be noted that, in this application, there is no specificconcept of X, Y, and Z coordinate axes in G-PCC. In general, on thebasis of the X, Y, and Z coordinate axes, the coordinate axis processingorder can be represented by 0, 1, and 2. For example, if the processingorder is the X-Y-Z order, it can be indicated by 0-1-2.

Based on Table 1 above, Table 2 is a correspondence table 2 betweenpreset indexes and processing orders. As illustrated in Table 2, fordifferent processing orders, a corresponding coordinate-axis-order indexcan be determined by querying the correspondence table between thepreset indexes and the processing orders.

Exemplarily, in this application, the decoder determines the processingorder of the point cloud data during point cloud decoding according tothe coordinate-axis-order index. If the value of thecoordinate-axis-order index is 0 or 4, that is, the processing order isindicated by 2-1-0, the decoder can determine that the correspondingprocessing order of the point cloud data is the Z-Y-X order. If thevalue of the coordinate-axis-order index is 1 or 7, that is, theprocessing order is indicated by 0-1-2, then the decoder can determinethat the corresponding processing order of the point cloud data is theX-Y-Z order. If the value of the coordinate-axis-order index is 2, thatis, the processing order is indicated by 0-2-1, the decoder candetermine that the corresponding processing order of the point clouddata is the X-Z-Y order. If the value of the coordinate-axis-order indexis 3, that is, the processing order is indicated by 2-0-1, the decodercan determine that the corresponding processing order of the point clouddata is the Y-Z-X order. If the value of the coordinate-axis-order indexis 5, that is, the processing order is indicated by 1-2-0, then thedecoder can determine that the corresponding processing order of thepoint cloud data is the Z-X-Y order. If the value of thecoordinate-axis-order index is 6, that is, the processing order isindicated by 1-0-2, the decoder can determine that the correspondingprocessing order of the point cloud data is the Y-X-Z order.

It is understandable that, in this application, thecoordinate-axis-order index can be represented by the syntaxaxis_coding_order, that is, the processing order of the three coordinateaxes X, Y, and Z can be specified by the syntax axis_coding_order.Specifically, based on the above Table 2, the axis_coding_order for theG-PCC standard can be used to process data in the RecPic[pointIdx][axis]buffer. For example, when the value of axis_coding_order is equal to 0,that is, the processing order is Z-Y-X, if the value of axis is equal to0, RecPic[pointIdx][0] stores data of the Z axis; if the value of axisis equal to 1, RecPic[pointIdx][1] stores data of the Y axis; if thevalue of axis is equal to 2, RecPic[pointIdx][2] stores data of the Xaxis.

At 203, the bitstream is parsed to obtain recovered data of the pointcloud data.

In the implementation of this application, the decoder can further parsethe bitstream to obtain the recovered data of the point cloud data.

At 204, a position of coordinate data of the point cloud data in astorage unit of the recovered data is determined according to theprocessing order.

In the implementation of this application, after the decoder determinesthe processing order of the point cloud data during point cloud decodingaccording to the coordinate-axis-order index and parses the bitstream toobtain the recovered data of the point cloud data, the decoder candetermine the position of the coordinate data of the point cloud data inthe storage unit of the recovered data according to the processingorder.

That is to say, in this application, the processing order indicates thecoordinate axis corresponding to data sequentially output by the decoderafter the inverse transform of RAHT (i.e., inverse RAHT) is performed onthe recovered data obtained through parsing the bitstream.

Furthermore, in the implementation of this application, when the decoderdetermines the position of the coordinate data of the point cloud datain the storage unit of the recovered data according to the processingorder, the decoder can, in the storage unit of the recovered data, for apoint in the point cloud data, obtain coordinate data of the pointaccording to a coordinate axis order indicated by the processing order.

It is understandable that, in this application, when RAHT is performed,based on the processing order of RAHT, the data obtained first issignalled into the data storage unit first, and the data obtained lateris signalled into the data storage unit later, that is, the signallingorder of the data corresponds to the coordinate axis order.

Specifically, in the implementation of this application, when thedecoder determines the position of the coordinate data of the pointcloud data in the storage unit of the recovered data according to theprocessing order, the decoder can perform sequentially, according to theprocessing order, RAHT on the point cloud data in a correspondingcoordinate axis direction.

It should be noted that, in this application, the execution process ofRAHT is to: first transform in one coordinate direction, then transformin another coordinate direction, and finally transform in the thirdcoordinate direction.

It should be noted that, in the implementation of this application, whenthe decoder performs sequentially, according to the processing order,RAHT on the point cloud data in the corresponding coordinate axisdirection, the decoder can parse the bitstream to determine a Mortoncode of a node in the point cloud data and perform RAHT on the pointcloud data according to the processing order and the Morton code.

Specifically, in the implementation of this application, the decoder canfirst calculate to obtain the Morton code of each node in the pointcloud data, then sort the nodes in the point cloud data according to anascending order of the Morton code, and finally traverse each node inthe point cloud data in the sorted order.

It can be understood that, in the implementation of this application,the processing order is the transform order when RAHT is performed onthe attribute information of the point cloud. Therefore, after thedecoder determines the processing order, it can use the processing orderto perform RAHT on the point cloud data.

It should be noted that, in the implementation of this application,since the point cloud data may be all data in the point cloud, theprocessing order may be the transform order of all data in the pointcloud. Furthermore, after determining the processing order, the decodercan sequentially perform RAHT on each point in the point cloud accordingto the processing order.

Furthermore, in the implementation of this application, since the pointcloud data may also be part of data in the point cloud, that is, thepoint cloud data may be data of any slice in the point cloud, theprocessing order can also be the transform order of part of data in thepoint cloud. Furthermore, after determining the processing ordercorresponding to a certain slice in the point cloud, the decoder cansequentially perform RAHT on each point in this slice according to theprocessing order.

That is to say, in this application, if the processing order is thetransform order of all data in the point cloud, the decoder can use thesame transform order to perform RAHT on the all data in the point cloud.If the processing order is the transform order of part of data in thepoint cloud, the decoder can use the same transform order to performRAHT on the part of data in the point cloud. For example, for data in aslice after partition, the same transform order can be used for RAHT.

Furthermore, in the implementation of this application, when the decoderperforms RAHT on the point cloud data according to the processing orderand the Morton code, the decoder may first compare the processing orderwith the preset order, to determine whether the processing order is asame as a preset order.

It can be understood that, in the implementation of this application,the preset order may be a default transform order pre-stored by thedecoder. For example, the decoder can set the Z-Y-X order as the presetorder.

Furthermore, in the implementation of this application, after thedecoder compares the processing order with the preset order, the decoderperforms RAHT on the point cloud data directly according to the presetorder and the Morton code, if the processing order is the same as thepreset order; the decoder performs RAHT on the point cloud dataaccording to the processing order and the Morton code, if the processingorder is different from the preset order.

It should be noted that, in implementations of this application, FIG. 13is schematic diagram 2 of an implementation process of point clouddecoding. As illustrated in FIG. 13, before the decoder parses thebitstream to obtain the coordinate-axis-order index, i.e., before 201,the method performed by the decoder for decoding the point cloud datafurther includes the following.

At 205, the bitstream is parsed to determine an order indicationparameter, where the order indication parameter is for indicatingwhether to use the preset order.

At 206, determine that the processing order is different from the presetorder, if a value of the order indication parameter is indicative of notusing the preset order.

At 207, determine that the processing order is the same as the presetorder, if the value of the order indication parameter is indicative ofusing the preset order.

In the implementation of this application, the decoder may firstdetermine the order indication parameter corresponding to the pointcloud data by parsing the bitstream, and then determine whether to usethe preset order for transform according to the order indicationparameter.

It should be noted that, in the implementation of this application, theorder indication parameter may be used to indicate whether to use thepreset order. That is, if the encoder uses the preset order fortransform, the order indication parameter obtained by the decoderthrough parsing can indicate that the preset order is used. If theencoder does not use the preset order for transform, the orderindication parameter obtained by the decoder through parsing canindicate that the preset order is not used.

Furthermore, in the implementation of this application, after thedecoder obtains the order indication parameter through parsing, if thevalue of the order indication parameter indicates that the preset orderis not used, the decoder needs to transform the point cloud dataaccording to the processing order; if the value of the order indicationparameter indicates that the preset order is used, the decoder cantransform the point cloud data according to the preset order.

Exemplarily, in this application, when the value of the order indicationparameter is 0, it can be indicated that the preset order is not used;when the value of the order indication parameter is set to 1, it can beindicated that the preset order is used.

It is understandable that, in this application, the order indicationparameter can be characterized by the syntaxattr_raht_order_default_flag. Specifically, if the value ofattr_raht_order_default_flag is equal to 1, it indicates that the presetorder is used; if the value of attr_raht_order_default_flag is equal to0, it indicates that the preset order is not used.

According to the point cloud decoding method proposed in the above steps201 to 207, the decoder no longer uses the fixed transform order toperform RAHT on the point cloud data, as proposed in the prior art. Forexample, the X-Y-Z order is used to perform RAHT on all point clouddata. Instead, during decoding the point cloud data, the processingorder corresponding to the point cloud data is determined before thetransform, and then the processing order is used to perform RAHT.

It can be understood that, in this application, from the perspective ofthe processing order of the three coordinates of X, Y, and Z, currently,in G-PCC, the decoder performs transform in a fixed order. In contrast,the point cloud decoding method proposed in this application canadaptively change the processing order of the decoder on the threecoordinates in G-PCC, thereby improving decoding efficiency.

It should be noted that, in this application, the flexibility of theprocessing order can be constrained to the sequence layer, and theentire point cloud can use the same coordinate processing order, thatis, partitions in the point cloud (such as slices) all use the samecoordinate processing order.

It is understandable that, in this application, the encoding end maypreprocess the point cloud data before encoding the point cloud data.Specifically, the encoder can reset the X, Y, and Z coordinate axes ofthe point cloud data and re-determine the processing order. Thereafter,the encoder encodes the preprocessed point cloud data, and from theperspective of display, indicates the preprocessing method at thesequence layer, that is, after encoding the coordinate-axis-order indexcorresponding to the processing order, the encoder signals the encodedbits into the bitstream. Therefore, after the bitstream is transmittedto the decoding end, the decoder decodes the bitstream to obtain thedecoded point cloud, and performs post-processing on the point cloudaccording to the preprocessing method indicated by the sequence layer.That is, the decoding end parses to obtain the coordinate-axis-orderindex, and determines the processing order indicated by thecoordinate-axis-order index, so that the X, Y, and Z coordinate axes ofthe point cloud data can be adaptively set.

Implementations of this application provide the point cloud decodingmethod. The decoder parses the bitstream to obtain thecoordinate-axis-order index. The decoder determines the processing orderof the point cloud data during point cloud decoding according to thecoordinate-axis-order index, where the processing order indicates thecoordinate axis processing order of the three-dimensional coordinates ofthe point cloud data and the point cloud data is all or part of data inthe point cloud. The decoder parses the bitstream to obtain therecovered data of the point cloud data. The decoder determines theposition of the coordinate data of the point cloud data in the storageunit of the recovered data according to the processing order. That is,in the implementations of this application, at the encoding side, theencoder can first determine the processing order of transformcorresponding to the point cloud data, signal the processing order intothe bitstream while performing RAHT according to the processing order,and transmit the processing order to the decoder. At the decoding side,the decoder parses the bitstream to obtain the processing order of thetransform corresponding to the point cloud data, so that RAHT can beperformed according to the processing order. It can be seen, in thepoint cloud encoding and decoding method provided in this application,for all or part of data in the point cloud, a fixed order is no longerused to perform RAHT, but a syntax element in the bitstream is used toindicate the processing order. In this way, the coordinate processingorder during coding can be changed adaptively and the transformefficiency of RAHT can be further fully showed. As such, the problem oflow transform efficiency can be solved and the coding efficiency can begreatly improved.

Based on the above implementation, another implementation of thisapplication provides a point cloud encoding and decoding method.Compared with the prior art, in the implementation of this application,the codec can change the fixed transform order, that is, change thedefault order which is not transmitted. No matter at the encoding end orthe decoding end, the processing order corresponding to the point clouddata is determined before RAHT is performed on the point cloud, and thenthe processing order is used for RAHT. The transform process at thedecoding end will be exemplified below.

Exemplarily, in an implementation, the decoder obtains the processingorder X-Y-Z of the point cloud data after parsing the bitstream. Thepoint cloud data is part of data in the point cloud, that is, a slice(s)in the point cloud, and the processing order is different from the fixedpreset order Z-Y-X. Thereafter, the decoder can sort the points in thecorresponding slice based on the Morton code.

In the octree node decoding process, the spatial position of points ineach occupied child is determined according to the number of duplicatepoints in each child and the use of direct coded positions. Refer to thefollowing.

for( child = 0; child < GeometryNodeChildrenCnt; child++ ) {   childIdx= GeometryNodeChildren[ child ];   x = 2 × xN + ( childIdx & 4 == 1 );  y = 2 × yN + ( childIdx & 2 == 1 );   x = 2 × zN + ( childIdx & 1 == 1);   for( i = 0; i < GeometryNodeDupPoints[child] + 1 ; i++,  PointCount++ ) {    PointPos[PointCount][0] = x;   PointPos[PointCount][1] = y;    PointPos[PointCount][2] = z;   }  if( direct_mode_flag ) {    for( i = 0; i <= num_direct_points_minus1;i++,    PointCount++ ) {     PointPos[PointCount][0] = x +PointOffsetX[i];     PointPos[PointCount][1] = y + PointOffsetY[i];    PointPos[PointCount][2] = z + PointOffsetZ[i];    }   }  }

In the point sorting process based on Morton code, the decoder parsesthe bitstream to obtain the array McodeBeforeSort[i], where i=0 . . .PointNum-1. Refer to the following.

for ( b=0; b< raht_depth; b++ ){   McodeBeforeSort[i] |=((PointPos[i][1]>>b) & 1) << (3 × b+2)   McodeBeforeSort[i] |=((PointPos[i][2]>>b) & 1) << (3 × b+1)   McodeBeforeSort[i] |=((PointPos[i][0]>>b) & 1) << (3 × b)  }

Generally, from the perspective of the encoding process or the encoder,a syntax element is signalled in the bitstream to indicate information.From the perspective of the decoding process or the decoder, the syntaxelement is parsed from the bitstream to obtain the indicatedinformation.

Exemplarily, in an implementation, the processing order may be signalledin the attribute parameter set syntax. That is, the decoder can obtainthe processing order by parsing the bitstream of the attribute parameterset, where the syntax of the attribute parameter set is illustrated inTable 4.

TABLE 4 Descriptor attribute_parameter_set( ) {  aps_attr_parameter_set_id ue(v)   aps_seq_parameter_set_id ue(v)  attr_coding_type ue(v)   aps_attr_initial_qp ue(v)  aps_attr_chroma_qp_offset se(v)   aps_slice_qp_delta_present_flag u(1) if( attr_coding_type == 1 ){   attr_raht_order_index u(3)  }  isLifting = ( attr_coding_type == 0 || attr_coding_type == 2) ? 1 : 0  if(isLifting) {    lifting_num_pred_nearest_neighbours ue(v)   lifting_max_num_direct_predictors ue(v)    lifting_search_range ue(v)   lifting_lod_regular_sampling_enabled_flag u(1)   lifting_num_detail_levels_minus1 ue(v) [Ed. The V6.0 code use thevariable without minus1. It should be aligned]    for( idx = 0; idx <=num_detail_levels_minus1;    idx++ ) {     if (lifting_lod_decimation_enabled_flag )      lifting_sampling_period[idx]ue(v)     else      lifting_sampling_distance_squared[idx] ue(v)    }  }   if( attr_coding_type == 0 )   lifting_adaptive_prediction_threshold ue(v)   lifting_intra_lod_prediction_num_layers ue(v)   }  aps_extension_present_flag u(1)   if( aps_extension_present_flag )   while( more_data_in_byte_stream( ) )     aps_extension_data_flag u(1)  byte_alignment( ) }

Specifically, in this application, the coordinate-axis-order indexattr_raht_order_index may indicate the processing order for the node,that is, the transform order of RAHT. In the bitstream, the value ofattr_raht_order_index can be 0, 1, 2, 3, 4, 5, 6, or 7. Based on theabove Table 1, the decoder can determine the corresponding processingorder based on attr_raht_order_index obtained through parsing.Thereafter, according to the processing order, the point sorting processbased on Morton code can be performed.

Exemplarily, in an implantation, in the attribute parameter set, a flagmay be first signalled to indicate whether to use the default transformorder, that is, whether to use the preset order. If the preset order isnot used, the coordinate-axis-order index attr_raht_order_index issignalled to indicate the transform order other than the preset order.

That is to say, in this application, the decoder can obtain the orderindication parameter after parsing the bitstream of the attributeparameter set. The order indication parameter is used to indicatewhether to use the preset order. The attribute parameter set syntax isillustrated in Table 5.

TABLE 5 Descriptor attribute_parameter_set( ) {  aps_attr_parameter_set_id ue(v)   aps_seq_parameter_set_id ue(v)  attr_coding_type ue(v)   aps_attr_initial_qp ue(v)  aps_attr_chroma_qp_offset se(v)   aps_slice_qp_delta_present_flag u(1) if( attr_coding_type == 1 ){   attr_raht_order_default_flag u(1)   if(attr_raht_order_default_flag == 0 ){      attr_raht_order_indexu(3)    }  }   isLifting = ( attr_coding_type == 0 || attr_coding_type== 2) ? 1 : 0   if(isLifting) {     lifting_num_pred_nearest_neighboursue(v)     lifting_max_num_direct_predictors ue(v)    lifting_search_range ue(v)    lifting_lod_regular_sampling_enabled_flag u(1)    lifting_num_detail_levels_minus1 ue(v) [Ed. The V6.0 code use thevariable without minus1. It should be aligned]     for( idx = 0; idx <=num_detail_levels_minus1;     idx++ ) {       if (lifting_lod_decimation_enabled_flag )       lifting_sampling_period[idx] ue(v)       else       lifting_sampling_distance_squared[idx] ue(v)     }   }   if(attr_coding_type == 0 )     lifting_adaptive_prediction_threshold ue(v)    lifting_intra_lod_prediction_num_layers ue(v)   }  aps_extension_present_flag u(1)   if( aps_extension_present_flag )    while( more_data_in_byte_stream( ) )       aps_extension_data_flagu(1)   byte_alignment( ) }

It is understandable that, in this application, the order indicationparameter can be characterized by the syntaxattr_raht_order_default_flag. Specifically, if the value ofattr_raht_order_default_flag is equal to 1, it indicates that the presetorder is used. If the value of attr_raht_order_default_flag is equal to0, it indicates that the preset order is not used.

Furthermore, in the implementation of this application, if the value ofattr_raht_order_default_flag is equal to 0, that is, the preset order isnot used, the decoder can further determine the processing order usedaccording to the coordinate-axis-order index attr_raht_order_indexobtained through parsing.

It is understandable that, in this application, if the preset order isthe X-Y-Z order, the value of the coordinate-axis-order indexattr_raht_order_index obtained by the decoder through parsing can beused to indicate the other five transform orders except for the X-Y-Zorder. That is, in this application, on the basis of determining theorder indication parameter attr_raht_order_default_flag, thecoordinate-axis-order index attr_raht_order_index is used to indicateother transform orders except for the preset order.

TABLE 6 coordinate-axis-order index processing order 0 Z-Y-X 1 X-Z-Y 2Y-Z-X 3 Z-X-Y 4 Y-X-Z

Furthermore, in this application, the coordinate-axis-order indexattr_raht_order_index indicates the order of RAHT (except for thedefault preset order) for the node, that is, indicates the processingorder. In the bitstream, the value of attr_raht_order_index can be equalto 0, 1, 2, 3 or 4. Table 6 is a correspondence table 3 between presetindexes and processing orders, where the preset order is X-Y-Z. Asillustrated in Table 6, based on the value of coordinate-axis-orderindex, the decoder can determine the corresponding processing order byquerying the correspondence table between the preset indexes and theprocessing orders.

Furthermore, in this application, after the decoder obtains the orderindication parameter attr_raht_order_default_flag by parsing thebitstream of the attribute parameter set, if the value ofattr_raht_order_default_flag is equal to 1, it indicates that the presetorder is used. Then, according to the preset order, the decoder canperform the point sorting process based on Morton code.

Furthermore, in this application, after the decoder obtains the orderindication parameter attr_raht_order_default_flag by parsing thebitstream of the attribute parameter set, if the value ofattr_raht_order_default_flag is equal to 0, it indicates that the presetorder is not used. Then, the decoder can continue to parse the bitstreamto obtain the coordinate-axis-order index attr_raht_order_index, anddetermine the processing order. Thus, according to the processing order,the point sorting process based on Morton code can be performed.

Exemplarily, in an implementation, the processing order is signalled inthe attribute parameter set, except that the descriptor of the syntaxelement attr_raht_order_index is ue(V) (i.e., Exp-Golomb codes). Fromthe perspective of encoding, the descriptor corresponds to the entropycoding method of the syntax element, while from the perspective ofdecoding, the descriptor corresponds to the parsing process of thesyntax element.

It is understandable that, in this application, the processing order ofRAHT is signalled in the attribute parameter set, which will be appliedin encoding or decoding one or more slices referring to this attributeparameter set.

Exemplarily, in an implementation, the processing order with or withoutthe preset order is signalled in the attribute slice header. Theattribute slice header syntax is illustrated in Table 7.

TABLE 7 Descriptor attribute_slice_header( ) {  ash_attr_parameter_set_id ue(v)   ash_attr_sps_attr_idx ue(v)  ash_attr_geom_slice_id ue(v)  if( attr_coding_type == 1 ){    ...  }  if (aps_slice_qp_delta_present_flag) {     ash_qp_delta_luma se(v)    ash_qp_delta_chroma se(v)   }   byte_alignment( ) }

It can be understood that, in this application, the processing ordersignalled in the attribute slice header is only used to encode or decodethis slice.

Exemplarily, in an implementation, the processing order with/without thepreset order is signalled in the attribute parameter set and theattribute slice header referring to this attribute parameter set. Theprocessing order signalled in the attribute slice header can overridethe processing order determined by parsing the attribute parameter set.

Specifically, in this application, the processing order is signalled inthe attribute parameter set, where the attribute parameter set syntax isillustrated in Table 8.

TABLE 8 Descriptor attribute_parameter_set( ) {  aps_attr_parameter_set_id ue(v)   aps_seq_parameter_set_id ue(v)  attr_coding_type ue(v)   aps_attr_initial_qp ue(v)  aps_attr_chroma_qp_offset se(v)   aps_slice_qp_delta_present_flag u(1) if( attr_coding_type == 1 ){    ...  }   isLifting = ( attr_coding_type== 0 || attr_coding_type == 2) ? 1 : 0   if(isLifting) {    lifting_num_pred_nearest_neighbours ue(v)    lifting_max_num_direct_predictors ue(v)     lifting_search_rangeue(v)     lifting_lod_regular_sampling_enabled_flag u(1)    lifting_num_detail_levels_minus1 ue(v) [Ed. The V6.0 code use thevariable without minus1. It should be aligned]     for( idx = 0; idx <=num_detail_levels_minus1;     idx++ ) {      if (lifting_lod_decimation_enabled_flag )       lifting_sampling_period[idx]ue(v)      else       lifting_sampling_distance_squared[ idx ] ue(v)    }   }   if( attr_coding_type == 0 )    lifting_adaptive_prediction_threshold ue(v)    lifting_intra_lod_prediction_num_layers ue(v)   }  aps_extension_present_flag u(1)   if( aps_extension_present_flag )    while( more_data_in_byte_stream( ) )      aps_extension_data_flagu(1)   byte_alignment( ) }

Furthermore, in the implementation of this application, the attributeslice header syntax is illustrated in Table 9.

TABLE 9 Descriptor attribute_slice_header( ) {  ash_attr_parameter_set_id ue(v)   ash_attr_sps_attr_idx ue(v)  ash_attr_geom_slice_id ue(v)  if( attr_coding_type == 1 ){  ash_attr_raht_order_override_flag u(1)  if(ash_attr_raht_order_override_flag == 1 )   ash_attr_raht_order_index u(3) (or ue(v))  }   if(aps_slice_qp_delta_present_flag) {    ash_qp_delta_luma se(v)   ash_qp_delta_chroma se(v)   }   byte_alignment( ) }

It is understandable that, in this application, the decoder can obtainthe syntax element ash_attr_raht_order_override_flag after parsing thebitstream. The syntax element ash_attr_raht_order_override_flag is usedto indicate whether to use the processing order signalled in theattribute parameter set.

Furthermore, in the implementation of this application, if the value ofash_attr_raht_order_override_flag is equal to 0, the processing ordersignalled in the attribute parameter set referred to by the slice isused.

Furthermore, in the implementation of this application, if the value ofash_attr_raht_order_override_flag is equal to 1, it indicates that theprocessing order indicated by ash_attr_raht_index is used. Then, thedecoder can obtain ash_attr_raht_index through parsing, to furtherdetermine the processing order used. Specifically, the decoder mayfurther obtain the processing order indicated by ash_attr_raht_indexthrough the above Table 1.

It can be understood that, in the implementation of this application, ifthe value of ash_attr_raht_order_override_flag is equal to 1, itindicates that the processing order indicated by ash_attr_raht_index isused. Then, the decoder can dynamically determine it by removing theprocessing order already signalled in the attribute parameter set (thatis, the active attribute parameter set) referring to the slice. Forexample, if the processing order signalled in the active attributeparameter set is Z-Y-X, the encoder or decoder can construct acorrespondence table between preset indexes and processing orders byusing orders other than the Z-Y-X order. In the bitstream, the value ofattr_raht_order_index can be equal to 0, 1, 2, 3 or 4. Table 10illustrates a correspondence table 4 between preset indexes andprocessing orders. If the processing order signalled in the activeattribute parameter set is Z-Y-X, as illustrated in Table 10, based onthe value of coordinate-axis-order indexash_attr_raht_index, the decodercan determine the corresponding processing order by querying thecorrespondence table between the preset indexes and the processingorders.

TABLE 10 coordinate-axis-order index processing order 0 X-Y-Z 1 X-Z-Y 2Y-Z-X 3 Z-X-Y 4 Y-X-Z

It is understandable that, in this application, ifash_attr_raht_order_index is ue(v) coded or parsed, the bits used torepresent ash_attr_raht_order_index in the bitstream can be saved.

Furthermore, in this application, when attr_coding_type is equal to 1 inthe attribute parameter set, the additional flag such asattr_raht_order_override_allowed_flag is signalled (from the perspectiveof the encoding or encoder) or parsed (from the perspective of thedecoding or decoder), to indicate whether the processing order of RAHTspecified in the attribute slice header referring to the attributeparameter set is allowed to override the processing order of RAHTspecified in the attribute parameter set. Forattr_raht_order_override_allowed_flag, the attribute slice header syntaxis illustrated in Table 11.

TABLE 11 Descriptor attribute_slice_header( ) {  ash_attr_parameter_set_id ue(v)   ash_attr_sps_attr_idx ue(v)  ash_attr_geom_slice_id ue(v)  if( attr_coding_type == 1 &&attr_raht_order_override_allowed_flag == 1){  ash_attr_raht_order_override_flag u(1)  if(ash_attr_raht_order_override_flag == 1 )   ash_attr_raht_order_index u(3) (or ue(v))  }   if(aps_slice_qp_delta_present_flag) {    ash_qp_delta_luma se(v)   ash_qp_delta_chroma se(v)   }   byte_alignment( ) }

Furthermore, in this application, after the decoder parses the bitstreamto obtain the processing order, the decoder can execute the Mortoncode-based point sorting process according to the preset order.

Implementations of this application provide the point cloud encoding anddecoding method, the encoder, the decoder, and the computer storagemedium. The encoder determines the processing order of point cloud dataduring point cloud encoding, where the processing order indicates thecoordinate axis processing order of the three-dimensional coordinates ofthe point cloud data and the point cloud data is all or part of data inthe point cloud. The encoder determines the coordinate-axis-order indexcorresponding to the processing order. The encoder encodes thecoordinate-axis-order index and signals the encoded bits into thebitstream. The encoder processes the point cloud data according to theprocessing order, to obtain the point cloud data to-be-encoded. Theencoder encodes the point cloud data to-be-encoded and signals theencoded bits into the bitstream. The decoder parses the bitstream toobtain the coordinate-axis-order index. The decoder determines theprocessing order of the point cloud data during point cloud decodingaccording to the coordinate-axis-order index, where the processing orderindicates the coordinate axis processing order of the three-dimensionalcoordinates of the point cloud data and the point cloud data is all orpart of data in the point cloud. The decoder parses the bitstream toobtain the recovered data of the point cloud data. The decoderdetermines the position of the coordinate data of the point cloud datain the storage unit of the recovered data according to the processingorder. That is, in the implementations of this application, at theencoding side, the encoder can first determine the processing order oftransform corresponding to the point cloud data, signal the processingorder into the bitstream while performing RAHT according to theprocessing order, and transmit the processing order to the decoder. Atthe decoding side, the decoder parses the bitstream to obtain theprocessing order of the transform corresponding to the point cloud data,so that RAHT can be performed according to the processing order. It canbe seen, in the point cloud encoding and decoding method provided inthis application, for all or part of data in the point cloud, a fixedorder is no longer used to perform RAHT, but a syntax element in thebitstream is used to indicate the processing order. In this way, thecoordinate processing order during coding can be changed adaptively andthe transform efficiency of RAHT can be further fully showed. As such,the problem of low transform efficiency can be solved and the codingefficiency can be greatly improved.

Based on the above implementations, in still another implementation ofthis application, FIG. 14 is schematic diagram 1 of a structure of anencoder. As illustrated in FIG. 14, an encoder 300 provided in theimplementation of this application includes a first determining part301, an encoding part 302, and a transform part 303.

The first determining part 301 is configured to determine a processingorder of point cloud data during point cloud encoding, where theprocessing order indicates a coordinate axis processing order ofthree-dimensional coordinates of the point cloud data and the pointcloud data is all or part of data in point cloud, and to determine acoordinate-axis-order index corresponding to the processing order.

The encoding part 302 is configured to encode the coordinate-axis-orderindex and signal encoded bits into a bitstream.

The transform part 303 is configured to process the point cloud dataaccording to the processing order, to obtain point cloud datato-be-encoded.

The encoding part 302 is further configured to encode the point clouddata to-be-encoded and signal encoded bits into the bitstream.

Furthermore, in an implementation of this application, the firstdetermining part 301 is configured to determine the processing orderaccording to a Morton code of a node in the point cloud data.

Furthermore, in an implementation of this application, the processingorder is any of a Z-Y-X order, an X-Y-Z order, an X-Z-Y order, a Y-Z-Xorder, a Z-X-Y order, and a Y-X-Z order, and X, Y, Z are coordinate axesof the three-dimensional coordinates of the point cloud data.

Furthermore, in an implementation of this application, the firstdetermining part 301 is further configured to set a value of thecoordinate-axis-order index corresponding to the processing orderaccording to a correspondence table between preset indexes andprocessing orders.

Furthermore, in an implementation of this application, thecorrespondence table between the preset indexes and the processingorders includes:

coordinate-axis-order index processing order 0 Z-Y-X order 1 X-Y-Z order2 X-Z-Y order 3 Y-Z-X order 4 Z-Y-X order 5 Z-X-Y order 6 Y-X-Z order 7X-Y-Z order.

Furthermore, in an implementation of this application, the encoding part302 is configured to encode the coordinate-axis-order index by usingfixed length coding.

Furthermore, in an implementation of this application, the encoding part302 is further configured to signal the encoded bits into a bitstreamcorresponding to a data unit of a parameter set, where the data unit ofthe parameter set contains parameters used for decoding the point clouddata

Furthermore, in an implementation of this application, the parameter setis a sequence-layer parameter set.

Furthermore, in an implementation of this application, the parameter setis a sequence parameter set.

Furthermore, in an implementation of this application, the data unit ofthe parameter set contains attribute information of the point clouddata, and the attribute information is a scalar attribute or a vectorattribute associated with a point in the point cloud data.

Furthermore, in an implementation of this application, the data unit ofthe parameter set contains geometry information of the point cloud data,and the geometry information is Cartesian coordinates associated with apoint in the point cloud data.

Furthermore, in an implementation of this application, the transformpart 303 is configured to perform coordinate mapping on the point clouddata according to the processing order.

Furthermore, in an implementation of this application, the transformpart 303 is further configured to rearrange the coordinates of the pointcloud data according to the processing order.

Furthermore, in an implementation of this application, the transformpart 303 is further configured to process sequentially, according to theprocessing order, the point cloud data in a corresponding coordinateaxis direction.

Furthermore, in an implementation of this application, the transformpart 303 is further configured to perform sequentially, according to theprocessing order, region adaptive hierarchical transform (RAHT) on thepoint cloud data in the corresponding coordinate axis direction.

Furthermore, in an implementation of this application, the transformpart 303 is further configured to determine a Morton code of a node inthe point cloud data, and perform RAHT on the point cloud data accordingto the processing order and the Morton code.

Furthermore, in an implementation of this application, the transformpart 303 is further configured to perform RAHT on the point cloud dataaccording to a preset order and the Morton code, if the processing orderis a same as the preset order, and perform RAHT on the point cloud dataaccording to the processing order and the Morton code, if the processingorder is different from the preset order.

Furthermore, in an implementation of this application, the firstdetermining part 301 is further configured to determine an orderindication parameter according to the processing order, where the orderindication parameter is for indicating whether to use the preset order,after determining the processing order of the point cloud data duringpoint cloud encoding and before determining the coordinate-axis-orderindex corresponding to the processing order. The encoding part 302 isfurther configured to encode the order indication parameter and signalencoded bits into the bitstream.

Furthermore, in an implementation of this application, the firstdetermining part 301 is further configured to set a value of the orderindication parameter to be indicative of not using the preset order, ifthe processing order is different from the preset order, and set thevalue of the order indication parameter to be indicative of using thepreset order, if the processing order is the same as the preset order.

Furthermore, in an implementation of this application, the encoding part302 is further configured to signal the encoded bits into a data unitwhere auxiliary information of the bitstream is located.

Furthermore, in an implementation of this application, the auxiliaryinformation is VUI.

Furthermore, in an implementation of this application, the auxiliaryinformation is SEI.

Furthermore, in an implementation of this application, the encoding part302 is further configured to signal the encoded bits into a transmissionstream containing point cloud encoding data corresponding to the pointcloud data.

Furthermore, in an implementation of this application, the encoding part302 is further configured to signal the encoded bits into a media filecontaining point cloud encoding data corresponding to the point clouddata.

FIG. 15 is schematic diagram 2 of a structure of an encoder. Asillustrated in FIG. 15, the encoder 300 provided in the implementationof this application can further include a first processor 304, a firstmemory 305 storing instructions executable by the first processor 304, afirst communication interface 306, and a first bus 307 for connectingthe first processor 304, the first memory 305, and the firstcommunication interface 306.

Furthermore, in the implementation of this application, the above firstprocessor 304 is configured to determine a processing order of pointcloud data during point cloud encoding, where the processing orderindicates a coordinate axis processing order of three-dimensionalcoordinates of the point cloud data and the point cloud data is all orpart of data in point cloud; determine a coordinate-axis-order indexcorresponding to the processing order; encode the coordinate-axis-orderindex and signal encoded bits into a bitstream; process the point clouddata according to the processing order, to obtain point cloud datato-be-encoded; and encode the point cloud data to-be-encoded and signalencoded bits into the bitstream.

If the integrated units are implemented as software functional units andsold or used as standalone products, they may be stored in a computerreadable storage medium. Based on such an understanding, the essentialtechnical solution, or the portion that contributes to the prior art, orall or part of the technical solution of this application may beembodied as software products. The computer software products can bestored in a storage medium and may include multiple instructions that,when executed, can cause a computing device, e.g., a personal computer,a server, a network device, etc., or a processor to execute some or alloperations of the methods described in various implementations. Theabove storage medium may include various kinds of media that can storeprogram codes, such as a universal serial bus (USB) flash disk, a mobilehard drive, a read only memory (ROM), a random access memory (RAM), amagnetic disk, or an optical disk.

Implementations of this application provide the encoder. The encoderdetermines the processing order of point cloud data during point cloudencoding, where the processing order indicates the coordinate axisprocessing order of the three-dimensional coordinates of the point clouddata and the point cloud data is all or part of data in the point cloud.The encoder determines the coordinate-axis-order index corresponding tothe processing order. The encoder encodes the coordinate-axis-orderindex and signals the encoded bits into the bitstream. The encoderprocesses the point cloud data according to the processing order, toobtain the point cloud data to-be-encoded. The encoder encodes the pointcloud data to-be-encoded and signals the encoded bits into thebitstream. That is, in the implementations of this application, at theencoding side, the encoder can first determine the processing order oftransform corresponding to the point cloud data, signal the processingorder into the bitstream while performing RAHT according to theprocessing order, and transmit the processing order to the decoder. Atthe decoding side, the decoder parses the bitstream to obtain theprocessing order of the transform corresponding to the point cloud data,so that RAHT can be performed according to the processing order. It canbe seen, in the point cloud encoding and decoding method provided inthis application, for all or part of data in the point cloud, a fixedorder is no longer used to perform RAHT, but a syntax element in thebitstream is used to indicate the processing order. In this way, thecoordinate processing order during coding can be changed adaptively andthe transform efficiency of RAHT can be further fully showed. As such,the problem of low transform efficiency can be solved and the codingefficiency can be greatly improved.

FIG. 16 is schematic diagram 1 of a structure of a decoder. Asillustrated in FIG. 16, a decoder 400 provided in the implementation ofthis application includes a parsing part 401 and a second determiningpart 402.

The parsing part 401 is configured to parse a bitstream to obtain acoordinate-axis-order index.

The second determining part 402 is configured to determine a processingorder of point cloud data during point cloud decoding according to thecoordinate-axis-order index, where the processing order indicates acoordinate axis processing order of three-dimensional coordinates of thepoint cloud data and the point cloud data is all or part of data inpoint cloud.

The parsing part 401 is further configured to parse the bitstream toobtain recovered data of the point cloud data.

The second determining part 402 is further configured to determine aposition of coordinate data of the point cloud data in a storage unit ofthe recovered data according to the processing order.

Furthermore, in the implementation of this application, the parsing part401 is configured to parse a fixed length code to obtain thecoordinate-axis-order index.

Furthermore, in the implementation of this application, the parsing part401 is further configured to parse a bitstream corresponding to a dataunit of a parameter set in the bitstream, where the data unit of theparameter set contains parameters used for decoding the point clouddata.

Furthermore, in the implementation of this application, the parameterset is a sequence-layer parameter set.

Furthermore, in the implementation of this application, the parameterset is a sequence parameter set.

Furthermore, in the implementation of this application, the data unit ofthe parameter set contains attribute information of the point clouddata, and the attribute information is a scalar attribute or a vectorattribute associated with a point in the point cloud data.

Furthermore, in the implementation of this application, the data unit ofthe parameter set contains geometry information of the point cloud data,and the geometry information is Cartesian coordinates associated with apoint in the point cloud data.

Furthermore, in the implementation of this application, the processingorder is any of a Z-Y-X order, an X-Y-Z order, an X-Z-Y order, a Y-Z-Xorder, a Z-X-Y order, and a Y-X-Z order, and X, Y, Z are coordinate axesof the three-dimensional coordinates of the point cloud data.

Furthermore, in the implementation of this application, the seconddetermining part 402 is configured to determine the processing ordercorresponding to the coordinate-axis-order index according to acorrespondence table between preset indexes and processing orders.

Furthermore, in the implementation of this application, thecorrespondence table between the preset indexes and the processingorders includes:

coordinate-axis-order index processing order 0 Z-Y-X order 1 X-Y-Z order2 X-Z-Y order 3 Y-Z-X order 4 Z-Y-X order 5 Z-X-Y order 6 Y-X-Z order 7X-Y-Z order.

Furthermore, in the implementation of this application, the seconddetermining part 402 is further configured to, in the storage unit ofthe recovered data, for a point in the point cloud data, obtaincoordinate data of the point according to a coordinate axis orderindicated by the processing order.

Furthermore, in the implementation of this application, the seconddetermining part 402 is further configured to perform sequentially,according to the processing order, region adaptive hierarchicaltransform (RAHT) on the point cloud data in a corresponding coordinateaxis direction.

Furthermore, in the implementation of this application, the seconddetermining part 402 is further configured to parse the bitstream todetermine a Morton code of a node in the point cloud data, and performRAHT on the point cloud data according to the processing order and theMorton code.

Furthermore, in the implementation of this application, the seconddetermining part 402 is further configured to perform RAHT on the pointcloud data according to a preset order and the Morton code, if theprocessing order is a same as the preset order, and performing RAHT onthe point cloud data according to the processing order and the Mortoncode, if the processing order is different from the preset order.

Furthermore, in the implementation of this application, the parsing part401 is further configured to parse the bitstream to determine an orderindication parameter, where the order indication parameter is forindicating whether to use the preset order, before parsing the bitstreamto obtain the coordinate-axis-order index.

The second determining part 402 is further configured to determine thatthe processing order is different from the preset order, if a value ofthe order indication parameter is indicative of not using the presetorder, and determine that the processing order is the same as the presetorder, if the value of the order indication parameter is indicative ofusing the preset order.

Furthermore, in the implementation of this application, the parsing part401 is further configured to parse a data unit where auxiliaryinformation of the bitstream is located, to obtain thecoordinate-axis-order index.

Furthermore, in the implementation of this application, the auxiliaryinformation is VUI.

Furthermore, in the implementation of this application, the auxiliaryinformation is SEI.

Furthermore, in the implementation of this application, the parsing part401 is further configured to parse a transmission stream containingpoint cloud encoding data, to obtain the coordinate-axis-order index.

Furthermore, in the implementation of this application, the parsing part401 is further configured to parse a media file containing point cloudencoding data, to obtain the coordinate-axis-order index.

FIG. 17 is schematic diagram 2 of a structure of a decoder. Asillustrated in FIG. 17, the decoder 400 of the implementation of thisapplication can further includes 400 may also include a second processor403, a second memory 404 storing executable instructions of the secondprocessor 403, a second communication interface 405, and a second bus406 for connecting the second processor 403, the second memory 404, andthe second communication interface 405.

Furthermore, in the implementation of this application, the above secondprocessor 403 is configured to parse a bitstream to obtain acoordinate-axis-order index, determine a processing order of point clouddata during point cloud decoding according to the coordinate-axis-orderindex, where the processing order indicates a coordinate axis processingorder of three-dimensional coordinates of the point cloud data and thepoint cloud data is all or part of data in point cloud, parse thebitstream to obtain recovered data of the point cloud data, anddetermine a position of coordinate data of the point cloud data in astorage unit of the recovered data according to the processing order.

If the integrated units are implemented as software functional units andsold or used as standalone products, they may be stored in a computerreadable storage medium. Based on such an understanding, the essentialtechnical solution, or the portion that contributes to the prior art, orall or part of the technical solution of this application may beembodied as software products. The computer software products can bestored in a storage medium and may include multiple instructions that,when executed, can cause a computing device, e.g., a personal computer,a server, a network device, etc., or a processor to execute some or alloperations of the methods described in various implementations. Theabove storage medium may include various kinds of media that can storeprogram codes, such as a USB flash disk, a mobile hard drive, a ROM, aRAM, a magnetic disk, or an optical disk.

Implementations of this application provide the decoder. The decoderparses the bitstream to obtain the coordinate-axis-order index. Thedecoder determines the processing order of the point cloud data duringpoint cloud decoding according to the coordinate-axis-order index, wherethe processing order indicates the coordinate axis processing order ofthe three-dimensional coordinates of the point cloud data and the pointcloud data is all or part of data in the point cloud. The decoder parsesthe bitstream to obtain the recovered data of the point cloud data. Thedecoder determines the position of the coordinate data of the pointcloud data in the storage unit of the recovered data according to theprocessing order. That is, in the implementations of this application,at the encoding side, the encoder can first determine the processingorder of transform corresponding to the point cloud data, signal theprocessing order into the bitstream while performing RAHT according tothe processing order, and transmit the processing order to the decoder.At the decoding side, the decoder parses the bitstream to obtain theprocessing order of the transform corresponding to the point cloud data,so that RAHT can be performed according to the processing order. It canbe seen, in the point cloud encoding and decoding method provided inthis application, for all or part of data in the point cloud, a fixedorder is no longer used to perform RAHT, but a syntax element in thebitstream is used to indicate the processing order. In this way, thecoordinate processing order during coding can be changed adaptively andthe transform efficiency of RAHT can be further fully showed. As such,the problem of low transform efficiency can be solved and the codingefficiency can be greatly improved.

Implementations of this application provide a computer readable storagemedium. The computer readable storage medium stores a program. Whenexecuted by a processor, the program implements the method of the aboveimplementations.

Specifically, program instructions corresponding to an encoding methodin this implementation can be stored in a storage medium such as anoptical disk, a hard disk, and a USB flash disk. When the programinstructions corresponding to the encoding method in the storage mediumare read or executed by an electronic device, the following operationsare implemented.

A processing order of point cloud data during point cloud encoding isdetermined, where the processing order indicates a coordinate axisprocessing order of three-dimensional coordinates of the point clouddata and the point cloud data is all or part of data in point cloud. Acoordinate-axis-order index corresponding to the processing order isdetermined. The coordinate-axis-order index is encoded and encoded bitsare signalled into a bitstream. The point cloud data is processedaccording to the processing order, to obtain point cloud datato-be-encoded. The point cloud data to-be-encoded is encoded and encodedbits are signalled into the bitstream.

Specifically, program instructions corresponding to a decoding method inthis implementation can be stored in a storage medium such as an opticaldisk, a hard disk, and a USB flash disk. When the program instructionscorresponding to the decoding method in the storage medium are read orexecuted by an electronic device, the following operations areimplemented.

A bitstream is parsed to obtain a coordinate-axis-order index. Aprocessing order of point cloud data during point cloud decoding isdetermined according to the coordinate-axis-order index, where theprocessing order indicates a coordinate axis processing order ofthree-dimensional coordinates of the point cloud data and the pointcloud data is all or part of data in point cloud. The bitstream isparsed to obtain recovered data of the point cloud data. A position ofcoordinate data of the point cloud data in a storage unit of therecovered data is determined according to the processing order.

Those skilled in the art will understand that implementations herein canprovide a method, a system, or a computer program product. Therefore,this application may have hardware-only implementations, software-onlyimplementations, or software plus hardware implementations. In addition,this application may be implemented in the form of a computer programproduct embodied on one or more computer usable storage media (includingbut not limited to a magnetic storage device, an optical memory, and thelike) including computer usable program codes.

This application is described herein with reference to schematicflowcharts and/or block diagrams of methods, apparatuses (systems), andcomputer program products according to the implementations of thisapplication. It should be understood that each flow and/or block in theflowchart and/or block diagram, and a combination of flow and/or blockin the flowchart and/or block diagram can be implemented by computerprogram instructions. These computer program instructions may beprovided to a general purpose computer, a special purpose computer, anembedded processor or a processor of other programmable data processingapparatuses to form a machine, such that devices for implementingfunctions specified by one or more flows in the flowchart and/or one ormore blocks in the block diagram may be generated by executing theinstructions with the processor of the computer or other programmabledata processing apparatuses.

The computer program instructions may also be stored in acomputer-readable memory that can direct the computer or otherprogrammable data processing apparatuses to operate in a given manner,so that the instructions stored in the computer-readable memory producea manufactured article including an instruction device, and theinstruction device implements the functions specified by one or moreflows in the flowchart and/or one or more blocks in the block diagram.

The computer program instructions may also be loaded onto the computeror other programmable data processing apparatuses, such that a series ofprocess steps may be executed on the computer or other programmableapparatuses to produce processing implemented by the computer, so thatthe instructions executed on the computer or other programmableapparatuses provide steps for implementing the functions specified byone or more flows in the flowchart and/or one or more blocks in theblock diagram.

The above are only preferred implementations of this application, andare not used to limit the protection scope of this application.

INDUSTRIAL APPLICABILITY

Implementations of this application provide a point cloud encoding anddecoding method, an encoder, a decoder, and a computer storage medium.The encoder determines the processing order of point cloud data duringpoint cloud encoding, where the processing order indicates thecoordinate axis processing order of the three-dimensional coordinates ofthe point cloud data and the point cloud data is all or part of data inthe point cloud. The encoder determines the coordinate-axis-order indexcorresponding to the processing order. The encoder encodes thecoordinate-axis-order index and signals the encoded bits into thebitstream. The encoder processes the point cloud data according to theprocessing order, to obtain the point cloud data to-be-encoded. Theencoder encodes the point cloud data to-be-encoded and signals theencoded bits into the bitstream. The decoder parses the bitstream toobtain the coordinate-axis-order index. The decoder determines theprocessing order of the point cloud data during point cloud decodingaccording to the coordinate-axis-order index, where the processing orderindicates the coordinate axis processing order of the three-dimensionalcoordinates of the point cloud data and the point cloud data is all orpart of data in the point cloud. The decoder parses the bitstream toobtain the recovered data of the point cloud data. The decoderdetermines the position of the coordinate data of the point cloud datain the storage unit of the recovered data according to the processingorder. That is, in the implementations of this application, at theencoding side, the encoder can first determine the processing order oftransform corresponding to the point cloud data, signal the processingorder into the bitstream while performing RAHT according to theprocessing order, and transmit the processing order to the decoder. Atthe decoding side, the decoder parses the bitstream to obtain theprocessing order of the transform corresponding to the point cloud data,so that RAHT can be performed according to the processing order. It canbe seen, in the point cloud encoding and decoding method provided inthis application, for all or part of data in the point cloud, a fixedorder is no longer used to perform RAHT, but a syntax element in thebitstream is used to indicate the processing order. In this way, thecoordinate processing order during coding can be changed adaptively andthe transform efficiency of RAHT can be further fully exhibited. Assuch, the problem of low transform efficiency can be solved and thecoding efficiency can be greatly improved.

What is claimed is:
 1. A point cloud encoding method, implemented in anencoder and comprising: determining a processing order of point clouddata during point cloud encoding, the processing order indicating acoordinate axis processing order of three-dimensional coordinates of thepoint cloud data and the point cloud data being all or part of data inpoint cloud; determining a coordinate-axis-order index corresponding tothe processing order; encoding the coordinate-axis-order index andsignalling encoded bits into a bitstream; processing the point clouddata according to the processing order, to obtain point cloud datato-be-encoded; and encoding the point cloud data to-be-encoded andsignalling encoded bits into the bitstream.
 2. The method of claim 1,wherein determining the processing order of the point cloud data duringpoint cloud encoding comprises: determining the processing orderaccording to a Morton code of a node in the point cloud data.
 3. Themethod of claim 1, wherein the processing order is any of a Z-Y-X order,an X-Y-Z order, an X-Z-Y order, a Y-Z-X order, a Z-X-Y order, and aY-X-Z order, and X, Y, Z are coordinate axes of the three-dimensionalcoordinates of the point cloud data.
 4. The method of claim 3, whereindetermining the coordinate-axis-order index corresponding to theprocessing order comprises: setting a value of the coordinate-axis-orderindex corresponding to the processing order according to acorrespondence table between preset indexes and processing orders. 5.The method of claim 4, wherein the correspondence table between thepreset indexes and the processing orders comprises:coordinate-axis-order index processing order 0 Z-Y-X order 1 X-Y-Z order2 X-Z-Y order 3 Y-Z-X order 4 Z-Y-X order 5 Z-X-Y order 6 Y-X-Z order 7X-Y-Z order.


6. A point cloud decoding method, implemented in a decoder andcomprising: parsing a bitstream to obtain a coordinate-axis-order index;determining a processing order of point cloud data during point clouddecoding according to the coordinate-axis-order index, the processingorder indicating a coordinate axis processing order of three-dimensionalcoordinates of the point cloud data and the point cloud data being allor part of data in point cloud; parsing the bitstream to obtainrecovered data of the point cloud data; and determining a position ofcoordinate data of the point cloud data in a storage unit of therecovered data according to the processing order.
 7. The method of claim6, wherein parsing the bitstream to obtain the coordinate-axis-orderindex comprises: parsing a fixed length code to obtain thecoordinate-axis-order index; or parsing a bitstream corresponding to adata unit of a parameter set in the bitstream, wherein the data unit ofthe parameter set contains parameters used for decoding the point clouddata.
 8. The method of claim 6, wherein the processing order is any of aZ-Y-X order, an X-Y-Z order, an X-Z-Y order, a Y-Z-X order, a Z-X-Yorder, and a Y-X-Z order, and X, Y, Z are coordinate axes of thethree-dimensional coordinates of the point cloud data.
 9. The method ofclaim 8, wherein determining the processing order of the point clouddata during point cloud decoding according to the coordinate-axis-orderindex comprises: determining the processing order corresponding to thecoordinate-axis-order index according to a correspondence table betweenpreset indexes and processing orders.
 10. The method of claim 9, whereinthe correspondence table between the preset indexes and the processingorders comprises: coordinate-axis-order index processing order 0 Z-Y-Xorder 1 X-Y-Z order 2 X-Z-Y order 3 Y-Z-X order 4 Z-Y-X order 5 Z-X-Yorder 6 Y-X-Z order 7 X-Y-Z order.


11. An encoder, comprising: at least one processor; and a memory coupledto the at least one processor and storing at least one computerexecutable instruction thereon which, when executed by the at least oneprocessor, causes the at least one processor to: determine a processingorder of point cloud data during point cloud encoding, the processingorder indicating a coordinate axis processing order of three-dimensionalcoordinates of the point cloud data and the point cloud data being allor part of data in point cloud; determine a coordinate-axis-order indexcorresponding to the processing order; encode the coordinate-axis-orderindex and signal encoded bits into a bitstream; process the point clouddata according to the processing order, to obtain point cloud datato-be-encoded; and encode the point cloud data to-be-encoded and signalencoded bits into the bitstream.
 12. The encoder of claim 11, whereinthe at least one processor configured to determine the processing orderof the point cloud data during point cloud encoding is configured to:determine the processing order according to a Morton code of a node inthe point cloud data.
 13. The encoder of claim 11, wherein theprocessing order is any of a Z-Y-X order, an X-Y-Z order, an X-Z-Yorder, a Y-Z-X order, a Z-X-Y order, and a Y-X-Z order, and X, Y, Z arecoordinate axes of the three-dimensional coordinates of the point clouddata.
 14. The encoder of claim 13, wherein the at least one processorconfigured to determine the coordinate-axis-order index corresponding tothe processing order is configured to: set a value of thecoordinate-axis-order index corresponding to the processing orderaccording to a correspondence table between preset indexes andprocessing orders.
 15. The encoder of claim 14, wherein thecorrespondence table between the preset indexes and the processingorders comprises: coordinate-axis-order index processing order 0 Z-Y-Xorder 1 X-Y-Z order 2 X-Z-Y order 3 Y-Z-X order 4 Z-Y-X order 5 Z-X-Yorder 6 Y-X-Z order 7 X-Y-Z order.


16. A decoder, comprising: at least one processor; and a memory coupledto the at least one processor and storing at least one computerexecutable instruction thereon which, when executed by the at least oneprocessor, causes the at least one processor to: parse a bitstream toobtain a coordinate-axis-order index; determine a processing order ofpoint cloud data during point cloud decoding according to thecoordinate-axis-order index, the processing order indicating acoordinate axis processing order of three-dimensional coordinates of thepoint cloud data and the point cloud data being all or part of data inpoint cloud; parse the bitstream to obtain recovered data of the pointcloud data; and determine a position of coordinate data of the pointcloud data in a storage unit of the recovered data according to theprocessing order.
 17. The decoder of claim 16, wherein the at least oneprocessor configured to parse the bitstream to obtain thecoordinate-axis-order index is configured to: parse a fixed length codeto obtain the coordinate-axis-order index; or parse a bitstreamcorresponding to a data unit of a parameter set in the bitstream,wherein the data unit of the parameter set contains parameters used fordecoding the point cloud data.
 18. The decoder of claim 16, wherein theprocessing order is any of a Z-Y-X order, an X-Y-Z order, an X-Z-Yorder, a Y-Z-X order, a Z-X-Y order, and a Y-X-Z order, and X, Y, Z arecoordinate axes of the three-dimensional coordinates of the point clouddata.
 19. The decoder of claim 18, wherein the at least one processorconfigured to determine the processing order of the point cloud dataduring point cloud decoding according to the coordinate-axis-order indexis configured to: determine the processing order corresponding to thecoordinate-axis-order index according to a correspondence table betweenpreset indexes and processing orders.
 20. The decoder of claim 19,wherein the correspondence table between the preset indexes and theprocessing orders comprises: coordinate-axis-order index processingorder 0 Z-Y-X order 1 X-Y-Z order 2 X-Z-Y order 3 Y-Z-X order 4 Z-Y-Xorder 5 Z-X-Y order 6 Y-X-Z order 7 X-Y-Z order.